feat(server): update to the compatible T3 Code release

[tarik02]

Problem

A paired server can run a different T3 Code release from the contracts bundled into t3cli. T3 Code clients resolve this by updating the server to the client's exact compatible version.

Scope

Add server update using the streamed server self-update RPC.

• Embed the exact T3 Code release represented by the upstream-t3code submodule in the CLI build.
• Use that compatible server version as the update target.
• Show the current and target versions before updating.
• Require interactive confirmation and support the standard non-interactive confirmation flag.
• Stream the downloading and installing stages.
• Treat the acknowledged restart disconnect as expected, then reconnect and verify the target server version.

Acceptance criteria

• A server already on the compatible version exits successfully without restarting.
• A supported background-service server updates and reconnects on the target version.
• Desktop-managed and unsupported server installations return the server's actionable guidance.
• An interrupted or failed update does not report success.

Out of scope

• Resolving the latest npm release independently of the bundled T3 Code version.
• Arbitrary target-version overrides in the first implementation.