Keep orbic-usb installer alive

### Prerequisites

- [x] I have read [CONTRIBUTING.md](https://github.com/EFForg/rayhunter/blob/main/CONTRIBUTING.md)

### What problem does this feature solve or what does it enhance?

Currently orbic-shell is on the path to deprecation.

In the past, we have organized parties locally where we bought and flashed several hundred orbics at a time to give out to people (or at least at cost for the hardware), which was really only possible due to the adb connection. Even with reflash failures we had a great hit rate.

Currently, manually connecting to each wifi hospot would terminate or at least cripple that workflow, as described in https://github.com/EFForg/rayhunter/issues/599#issue-3414980129

Are there any plans for maintaining the capability for batch flashing? It seems like a webUI RCE would need to be found, or more work put into rootshell, which I realize would be more overhead and maintenance.

### Proposed Solution

Offer a batch-flashing capability for Orbic.

### Alternatives Considered

_No response_

Start by reading issue #599 and tracing the existing orbic-usb installer alongside orbic-shell, rootshell, and the webUI/RCE approach mentioned here. Determine which path can preserve batch flashing without manually connecting to each hotspot; done means a supported batch-flashing workflow is implemented or its required scope is clearly established.

Written by the indexing model from the issue text.