chore: update third-party dependencies

[ovitrif]

Parent: #1113
Depends on: #1114 and #1115

Goal

Bring every directly versioned third-party library, BOM, and Gradle plugin in gradle/libs.versions.toml to its latest upstream release available when implementation begins and integrate all resulting API and behavior changes.

bitkit-core, ldk-node, vss-rust-client-ffi, and paykit-rs remain internal application dependencies with their own release and provenance workflows.

Deliverables

• Inventory every external library, BOM, and plugin declared in gradle/libs.versions.toml.
• Research the latest upstream release for each entry when implementation begins.
• Update every directly versioned third-party entry to that release.
• Verify BOM-managed libraries through their selected BOMs.
• Incorporate the landed AGP/KSP/Hilt and Kotlin/Compose versions from chore: upgrade to agp 9 and configure parallelism #1114 and chore: update kotlin and compose bom #1115 into the full catalog audit.
• Make every required source, manifest, resource, ProGuard/R8, test, build-script, and workflow change.
• Add focused regression coverage for each integration behavior changed by an upgrade.
• Record a PR table with dependency, previous version, selected version, primary release source, migration notes, and verification.

Version discovery, compatibility research, migration sequencing, and integration edits belong to implementation. This issue deliberately defines the catalog-wide outcome without freezing future “latest” version numbers.

Acceptance criteria

• Every directly versioned third-party entry in gradle/libs.versions.toml resolves to the latest upstream release available when implementation begins.
• Every BOM-managed dependency resolves through the latest selected BOM without an older direct override.
• The PR catalog table accounts for every third-party library, BOM, and plugin entry.
• The catalog contains no stale duplicate version keys or unused aliases.
• Dependency insight reports show one coherent resolved version for every upgraded family.
• Every required API and behavior migration is implemented and covered by focused tests.
• ./gradlew dependencies and targeted dependencyInsight checks complete without unexpected conflicts or forced downgrades.
• just compile, just test, just lint, just build, and just test android pass.
• Representative app and E2E journeys pass.
• Release assembly, shrinking, packaging, native bindings, Firebase, Room, Hilt, WorkManager, navigation, camera, widgets, networking, and hardware-wallet flows retain verified behavior.