feat(lora): consume region→preset compatibility map + TINY presets (protobufs #951)

[jamesarich]

Firmware now advertises which modem presets are legal in each LoRa region during the config handshake (protobufs#951 / firmware#10736). This wires the Android client to consume that map so the preset picker is constrained per region, amateur-only presets are gated, and the two new TINY presets are handled — preventing users from selecting an illegal region/preset combination.

⚠️ Preview / do not merge yet. This tracks org.meshtastic:protobufs:develop-SNAPSHOT to pick up #951, which isn't in a tagged release. Re-pin to a released protobufs and drop the resolution force (see Chores) once #951 ships in a tag.

🌟 New Features

• Decode and persist FromRadio.region_presets (LoRaRegionPresetMap) as session-scoped state, mirroring the deviceUIConfig handshake lifecycle (repository flow + handler dispatch + cleared on each new handshake).
• The LoRa config screen filters the modem-preset dropdown to the presets legal in the selected region; changing region snaps an illegal current preset to the region's default_preset.
• Licensed-only regions (amateur bands) render their presets greyed/non-selectable unless the device is a licensed operator, with an explanatory summary.
• Add the two new amateur-radio modem presets TINY_FAST / TINY_SLOW (15.625 kHz).
• Gracefully falls back to the full unconstrained preset list when the firmware predates this message (< 2.8) or a region has no map entry.

🛠️ Refactoring & Architecture

• Region→preset decoding lives in a pure core/model helper (RegionPresetConstraint), unit-testable off-Compose; the UI stays declarative.
• DropDownItem gains a defaulted enabled flag so individual menu items can render disabled.
• A firmware-applied region change (e.g. EU sibling swap — applied live, no reboot) is reflected when the LoRa screen is re-opened; the LoRa write is no longer applied optimistically, so the form never shows a requested-but-not-applied region.

🧹 Chores

• Track org.meshtastic:protobufs:develop-SNAPSHOT and force the transitive takpacket-sdk protobufs pin to match (root build.gradle.kts). Preview-only — revert with the re-pin above.

Testing Performed

• LoRaRegionPresetsTest (new): decode + repair + gate — null map / absent region / out-of-range index / empty group → unconstrained; legal-kept / illegal→default / default-fallback; licensed gate on/off.
• FromRadioPacketHandlerImplTest: region_presets routes to the handler.
• MeshConfigFlowManagerImplTest: region map cleared on new handshake.
• MeshConfigHandlerImplTest: handler→repository delegation.
• RadioConfigViewModelTest: map flow→state, localIsLicensed from the node, and LoRa setConfig is not applied optimistically / issues no re-read.
• ChannelOptionTest stays green (TINY presets mapped). Full allTests + test + detekt + spotlessCheck + assembleDebug pass locally.

🤖 Generated with Claude Code

[github-actions]

📄 Docs staleness check — advisory

This PR modifies user-facing UI source files but does not update any page under docs/en/user/ or docs/en/developer/.

⚠️ Doc changes propagate to 3 consumers: in-app docs browser, Jekyll site (GitHub Pages), and meshtastic.org (Docusaurus sync). Updating a page in docs/en/ automatically flows to all three.

Changed source files:

core/ui/src/commonMain/kotlin/org/meshtastic/core/ui/component/DropDownPreference.kt
core/ui/src/commonMain/kotlin/org/meshtastic/core/ui/util/ModelExtensions.kt
feature/settings/src/commonMain/kotlin/org/meshtastic/feature/settings/radio/component/LoRaConfigItemList.kt

What to check:

Changed area	Likely doc page
feature/messaging/	docs/en/user/messages-and-channels.md
feature/node/	docs/en/user/nodes.md or docs/en/user/node-metrics.md
feature/map/	docs/en/user/map-and-waypoints.md
feature/connections/	docs/en/user/connections.md
feature/settings/	docs/en/user/settings-radio-user.md or docs/en/user/settings-module-admin.md
feature/firmware/	docs/en/user/firmware.md
feature/intro/	docs/en/user/onboarding.md
feature/discovery/	docs/en/user/discovery.md
feature/docs/	Internal docs infrastructure
core/ui/	docs/en/developer/codebase.md or component-specific user pages

New page checklist (if adding a new doc page):

1. Create the .md file in docs/en/user/ or docs/en/developer/ with last_updated frontmatter
2. Register in DocBundleLoader.kt with string resources (in-app browser)
3. Jekyll and Docusaurus sync pick up new pages automatically — no config change needed

If this PR does not require a doc update (e.g., internal refactor, bug fix, test change), add the skip-docs-check label to dismiss this check.

Cross-platform note: This check is advisory while doc coverage matures. Both Android and Apple repos use the same skip-docs-check label and advisory severity. See meshtastic/design standards for shared conventions.

[github-actions]

🖼️ Preview staleness check — advisory

This PR modifies UI composables but does not update any *Previews.kt files.

Previews power screenshot tests and in-app docs screenshots. Keeping them current ensures visual regression coverage stays accurate.

Changed UI files:

feature/settings/src/commonMain/kotlin/org/meshtastic/feature/settings/radio/component/LoRaConfigItemList.kt

What to check:

Pattern	Preview file convention
feature/{name}/…/ui/ or component/	feature/{name}/…/*Previews.kt
core/ui/…/	core/ui/…/ (previews colocated)

Adding previews checklist:

1. Create or update a *Previews.kt file in the same module with @PreviewLightDark
2. Add @Suppress("PreviewPublic") if the preview is consumed by screenshot-tests
3. Add corresponding @PreviewTest function in screenshot-tests/src/screenshotTest/
4. Run ./gradlew :screenshot-tests:updateDebugScreenshotTest to generate reference images

If this PR does not require preview updates (e.g., logic-only change, non-visual refactor), add the skip-preview-check label to dismiss.

[codecov]

❌ 1 Tests Failed:

Tests completed	Failed	Passed	Skipped
2910	1	2909	0

View the top 1 failed test(s) by shortest run time

org.meshtastic.core.data.repository.DeviceLinkRepositoryImplTest::reconcilePrunesShortCodesNoLongerInCatalog()[jvm]

Stack Traces | 0.122s run time

org.opentest4j.AssertionFailedError: expected: <[a]> but was: <[a, b]>
	at kotlin.test.junit5.JUnit5Asserter.assertEquals(JUnitSupport.kt:32)
	at kotlin.test.AssertionsKt__AssertionsKt.assertEquals(Assertions.kt:63)
	at kotlin.test.AssertionsKt.assertEquals(Unknown Source)
	at kotlin.test.AssertionsKt__AssertionsKt.assertEquals$default(Assertions.kt:62)
	at kotlin.test.AssertionsKt.assertEquals$default(Unknown Source)
	at org.meshtastic.core.data.repository.DeviceLinkRepositoryImplTest$reconcilePrunesShortCodesNoLongerInCatalog$1.invokeSuspend(DeviceLinkRepositoryImplTest.kt:172)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:34)
	at kotlinx.coroutines.UndispatchedCoroutine.afterResume(CoroutineContext.kt:278)
	at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:101)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:47)
	at kotlinx.coroutines.internal.DispatchedContinuationKt.resumeCancellableWithInternal(DispatchedContinuation.kt:384)
	at kotlinx.coroutines.DispatchedCoroutine.afterResume(Builders.common.kt:588)
	at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:101)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:47)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100)
	at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:124)
	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:586)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:798)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:717)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:704)

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}