Add basic CDP support to inspector with a sample domain

[yorkie]

Overview

Add basic Chrome DevTools Protocol (CDP) support to the JSAR Runtime inspector, enabling CDP clients (such as Chrome DevTools) to connect via WebSocket and interact with the runtime.

Goals

• The inspector should expose a WebSocket endpoint compatible with the CDP standard, allowing third-party tools to connect.
• Implement minimal CDP handshake and message dispatch so that CDP messages can be parsed and responded to correctly.
• Provide at least one simple sample domain (such as MyExample or Runtime) with a basic method, so the client can verify connectivity and method invocation.
• Ensure the design is easily extensible for more domains in the future.

Technical Suggestions

• Refer to the Chrome DevTools Protocol documentation.
• Encapsulate CDP logic in an independent module for maintainability and future expansion.
• The CDP endpoint should be enabled by default with inspector, or optionally via configuration.

Acceptance Criteria

• A CDP client (e.g., Chrome DevTools or a simple CDP client script) can connect and invoke the implemented sample domain method(s).
• Inspector logs relevant CDP connection and invocation events for debugging.

---

Further domains or methods can be added in later iterations as needed.