Fix query and update handler argument contracts

[rmcdaniel]

Change

Addresses #70 by declaring the positional argument vectors that ordinary Rust query and update callbacks accept. Both JSON and lossless Avro registration paths now publish a complete, sorted contract for every advertised handler.

The low-level registration API still preserves explicitly supplied metadata. Unsupported update validators still fail before transport. Server's admission requirements stay intact. Existing runs keep the declarations captured when they started.

Prepare patch release 3.2.2. This changes registration metadata without changing the codec, wire commands or replay primitives.

Verification

• Regression coverage checks the actual registration request for JSON and lossless Avro query and update handlers, including argument shape and ordering.
• Update the existing live-poller contract expectation.
• Supported Rust 1.86/stable, package, documentation, corpus and official Avro consumer checks passed on bff3d65.
• The new registration regression also passed in a Rust 1.86 container. Formatting passed locally and in CI.
• After publication, rerun all nine PHP/Python/Rust client and handler directions in Sample App #153, including Rust replacement, duplicate identity and failed-update checks.

Published follow-through is complete through Rust 3.3.0's explicit signal declarations and merged Sample App #153. Main's full update experiment, all twelve timer/recovery cells and both native published-image checks pass. #70 is closed after this delivery.

Consumers

Sample App's Rust worker and its qualified tuple need 3.2.2 for the new live update experiment. PHP/Python SDKs and Server keep their published versions because their command and codec contracts are unchanged. Cloud qualification remains in its private repository.