Monitor Part 2 of 5 - Simplify Monitor Controls UI

[tekstrand]

Parts

1. AudioDevices extraction (Monitor status bar 1/5: Extract audio device handling into AudioDevices #90, merged)
2. The status strip itself, with the audio picker behind an overflow menu (this PR)
3. Rig link indicator on the strip, fed by a new rig status broadcast
4. Error state display (might combine with 3)
5. The same audio device selection in Settings

What

1. Replaces the status card with a two row strip under the waterfall: state dot and word, frequency button and engine switch, then power, TX offset and time drift on one line
2. Moves the audio device picker, clock sync and drift reset behind an overflow menu
3. Replaces the frequency dropdown with a text button that opens a single choice dialog
4. Shows Transmitting on the dot and state word while a send is on the air
5. Moves the release version into a new About category in Settings

Why

1. Inneficient use of screen real estate
2. Sync, reset, and the device picker are less common actions, move to a menu instead of permanent screen space
3. The exposed dropdown had a filter on restore bug that emptied the frequency list after a tab switch
4. Transmit is not a mode you switch. Messages go out per frame, so it shows as state, not as a control.
5. Not important for the home page

I specifically left out selectFrequency being part of the service because the code is tied closely with part 3 and it makes more sense to combine into that, IMO.

Test

1. ./gradlew :app:testDebugUnitTest
2. ./gradlew :app:assembleDebug on the Fire HD 10 and Pixel 7 profile emulators: the switch starts and stops the engine with the dot and state word tracking it, the overflow shows its three actions, the audio picker and frequency dialog both open and select, the strip fits phone landscape next to the nav rail, and with rig_type=qmx_serial the band profile still filters the preset list.

Screenshots

Tablet

Before

After

Phone

Before

After

[punk-kaos]

I found one UI-state edge case in renderState().

Right now it returns early when the label/color haven’t changed, but the power switch sync happens after that return. That means the switch can stay visually ON while the engine is actually OFF — for example, if the user turns it on, gets the mic permission prompt, then denies permission. The denial handler calls renderState(), but because the state is still STOPPED, the cached label/color match and it returns before resetting the switch.

I’d keep the label/dot repaint optimization, but move the powerSwitch.isChecked = shouldBeOn sync outside the early return so it always reflects the actual engine state.

[tekstrand]

@punk-kaos ♻️