Add Wear OS prompt handoff to Android sample

[jebrans]

Summary

• connect the existing Wear OS sample to the mobile-2 phone sample with an encoded typeagentchat://main prompt handoff
• add connection-aware phone handling that preserves prompts and prevents external input from answering pending confirmations
• modernize Wear speech recognition and surface remote-launch success or failure
• document the fire-and-forget POC boundary and the switch for disabling automatic execution

Design

This intentionally keeps the two existing Android samples as separate Gradle projects and keeps the phone as the only TypeAgent client. The watch is a thin input peripheral. Automatic execution defaults on for the POC and can be disabled with -Ptypeagent.wear.autoexecute=false.

RemoteActivityHelper requires a browsable deep link, so this is not a production authentication boundary. A production implementation should use the Wear Data Layer before enabling automatic execution broadly.

Validation

• mobile-2: :app:testDebugUnitTest, :app:assembleDebug, :app:lintDebug
• wearos: :app:assembleDebug, :app:lintDebug
• 252 mobile unit tests pass, including malformed-link, pending-confirmation, disconnected, and rejected-send cases

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[jebrans]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[jebrans]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).