Feature/tasker bridge

[malys]

Extract a shared MG4Hardware layer + add a profile bridge for a companion app

What this is

Building on the audit branch, this extracts MG4Control's vehicle-access layer into a
standalone, reusable library (MG4Hardware) and adds
a narrow, signature-protected external control API (ProfileControlService /
IProfileControl) so any app signed with the platform key can list and apply MG4Control
profiles over IPC. It also modernises the toolchain and hardens a few manifest items.

It is a sizeable, structural change. None of it is vehicle-tested — I do not have a car
to validate on — so please treat the on-vehicle checklist below as required before merging.

The commits

Commit	What
refactor: consume shared MG4Hardware library via git submodule	Move MG4Hardware, VehicleWriteGate, FirmwareInfo, AppLogger, and the driving models out of the app into the shared library, vendored as a submodule at ./MG4Hardware and consumed as the :mg4hardware Gradle subproject. VehicleWriteGate no longer references the app's R (message provider). Every gated setter now carries a @RequiresStandstill marker, asserted by a test.
feat: ProfileControlService — narrow external control API	A signature-permission-protected service exposing only listProfiles() + applyProfile(id). No raw property write, no snapshot read. Caller-agnostic: any app signed with the platform key can bind. VEHICLE_POWER_OFF stays out of reach.
build: migrate to AGP 9.1.1 / Gradle 9.3.1 / built-in Kotlin	compileSdk 34 → 36, drop the standalone Kotlin plugin, replace the removed applicationVariants output API (release naming moved to CI).
security: harden manifest + scope SAST to source	allowBackup=false, taskAffinity="" on the launcher (StrandHogg); SAST scans app/src only, not build/.
chore: remove the dead MG4Tasker ignition broadcast + refactor: trim the Tasker bridge to profile-only	The companion app became independent (it reads/writes the vehicle itself), so the ignition broadcast and the bridge's snapshot/action methods were removed.
refactor: generalize the Tasker bridge into a caller-agnostic profile API	Rename the now profile-only surface so its name no longer implies a single caller: ITaskerBridge→IProfileControl, TaskerBridgeService→ProfileControlService, permission …TASKER_BRIDGE→…CONTROL_PROFILES (package com.mg4.control.api). Behaviour identical.
chore: bump MG4Hardware … (several)	Submodule pointer bumps: English translation of the library, a WINDOW_POS property-id fix confirmed against the R69 sources (0x13340BC0 → 0x13400BC0), minSdk alignment, AAR publishing.

Full diff: 56 files, ~4.6k insertions / ~4.0k deletions (most of the deletion count is
files moving into the submodule).

Why extract the hardware layer

MG4Control, the ABRP telemetry app, and the new tasker app all need the same reflection
layer, the same 0 km/h gate, and the same per-generation routing. Keeping three copies
guarantees drift. The library is the single source of truth; the safety gate and the
per-firmware dispatch live in exactly one place.

What is unchanged

MG4Control's behaviour is intended to be identical — this is a structural move, not a
feature change. The profile logic, the hardkey handling, the OTA path, and the flavors are
untouched.

⚠️ Please verify on a vehicle before merging

The changes that cannot be validated off the car:

• The AGP 9 / R8 bump. A new major R8 shrinks/obfuscates the reflection-heavy code;
  the keep rules moved into the library's consumer-rules.pro. Needs a full on-vehicle
  release check (Katman1/2/3, HVAC, ADAS/AEB/ELK, ignition, OTA).
• The submodule extraction. Reflection targets and the system_uid path must still
  resolve identically after the package move (com.mg4.control.hardware →
  com.mg4.hardware).
• The WINDOW_POS id fix and the climate reads — derived from the R69 sources, not
  confirmed live on any generation.

Notes for you as the owner

• This introduces a git-submodule dependency on malys/MG4Hardware. If you would
  rather not take that on upstream, I am happy to instead vendor the library sources
  directly, or keep this as a fork-only change — your call.
• The tasker app and the ABRP app are separate repos; nothing here requires them.
• Commit authorship and the co-author trailer are on each commit.

Happy to split this into smaller PRs (library extraction / AGP bump / bridge) if that is
easier to review.