Upgrade extending-a-journey sample to 2026.03-LTS.

[rmanacmol]

Bump BOM, Gradle, and journey versions in place so the custom Contacts XML sample compiles on MDS 9 without merging main.

This PR is an LTS upgrade of the catalog sample, not a feature change and not Compose.

Target branch: sample/devs/extending-a-journey
Head: feature/OKR-2777-focused-lts-extending-a-journey (one commit: Upgrade extending-a-journey sample to 2026.03-LTS.)

What that sample branch is today

sample/devs/extending-a-journey is a maintained catalog sample. It shows how to extend a Backbase journey without rewriting the whole app:

• A custom Contacts list + detail UI (XML fragments) instead of using the stock Contacts journey screens as-is
• Wiring through More Menu, navigation, and Koin (contactsModule())
• A custom Accounts use case as a second “extend the journey” example

CATALOG.md currently still lists that sample as LTS 25.03. main is already on 2026.03-LTS (#51). This sample was left behind.

Purpose of the PR

Bring this sample up to 2026.03-LTS so it still builds and runs against the same SDK/MDS stack as main, while keeping the sample’s own Contacts/Accounts extension code.

Area	What changes
Versions	BOM 2026.03.1-LTS, contacts journey 8.3.0, other journeys/clients to LTS, Gradle 9.0.0, compileSdk 36
MSDK init	config.json-style init → AppConfigurationProvider / ConfigurationProvider (same API as current main)
MDS 9	Theme/header APIs (StatusBarColorProvider, TabListConfigurationProvider, PresentationModule)
Compatibility	Extra attrs so Contacts 8.x / accounts layouts still link against MDS 9 (iconBackground, colorOnSurfaceSecondary, etc.)
Catalog	Sample status line: LTS 26.03

After merge, someone who checks out sample/devs/extending-a-journey still sees the same custom Contacts screens, but they compile on 2026.03-LTS.

Local-only bits (dev URLs, API key, debug keystore in app/build.gradle.kts) are not part of that commit and should stay out of the PR.

Summary

Focused 2026.03-LTS upgrade of sample/devs/extending-a-journey without merging main.

This sample still shows how to keep a Backbase journey’s data layer and replace its UI: More → Contacts opens the custom XML contact list/detail, backed by ContactsUseCase (contacts-journey 8.3.0).

What changed (22 files)

• BOM 2025.03.01 → 2026.03.1-LTS; Gradle 9.0.0; compileSdk 36
• Journey pins aligned with LTS (auth 10, more-menu 9, workspaces 10.1, feature-filter 10, contacts 8.3.0)
• Local catalogs keep explicit versions (no remote midTierLibs.bundles.bomOutput)
• MSDK init: AppConfigurationProvider / ConfigurationProvider
• MDS 9 compatibility attrs (iconBackground, colorOnSurfaceSecondary)
• Header / presentation API updates required to compile
• CATALOG.md: this sample marked LTS 26.03

Explicitly not in this PR

• Merge of main (accounts-demo, accounts-test-data, E2E, README rewrite)
• Compose migration (separate follow-up)

Test plan

• :app:assembleDebug
• :accounts-journey:testDebugUnitTest
• :app:compileDebugAndroidTestKotlin
• Log in → More → Contacts: custom list, search, tap detail stub
• Confirm accounts tab and more menu still work

Screen_recording_20260904_114357.webm