Add support for connecting physical Android devices for development and testing.

Why it’s needed:
The current browser-based remote emulator is helpful, but it's often:

Laggy and slow, making development inefficient.

Lacking key hardware features such as camera, microphone, sensors, etc.

Insufficient for testing real-world performance and hardware interactions.

Suggested Approaches:

Allow ADB Bridge Support:
Enable the web editor to detect and interact with ADB-connected devices on the developer's local machine (e.g., via a local companion app or browser extension).

WebUSB/Web Serial Integration:
Use WebUSB or similar browser APIs to let the editor communicate directly with physical Android devices.

Firebase CLI Companion:
Provide a lightweight desktop Firebase agent/CLI that acts as a proxy between the browser editor and physical devices connected via ADB.

Impact:

Drastically improves testing accuracy and development speed.

Makes it possible to test features requiring real hardware access (camera, mic, sensors, network).

Closes the gap between browser-based IDEs and native/local development setups.