Add per-command metadata propagation to interfaces

[jwalters2]

Replaces #3666, whose original head fork was deleted.

Problem

Command callers sometimes need to attach correlation and workflow metadata to a single command and make that metadata available to the interface that writes the packet. Previously, the cmd API did not provide a supported way to carry caller metadata through command topics, queues, and command retries.

Changes

• Add an optional extra Hash/dict to the Ruby and Python cmd API families and scripting wrappers.
• JSON-encode extra on the command topic and merge it into command.extra before the interface writes the packet.
• Preserve metadata through command queues and hazardous-command retries.
• Use the COSMOS JSON encoders for queued metadata so binary values and special numeric values follow the same serialization rules as command parameters.
• Keep COSMOS-owned audit fields authoritative. Caller values cannot override cmd_string, username, interface_name, queue_username, or approver.
• Accept both serialized metadata and the earlier raw-Hash queue representation when processing queued commands.
• Document extra usage for Ruby and Python scripts.

Commands.build_cmd continues to clear template packet metadata. Caller metadata is applied only to the newly built command inside InterfaceMicroservice, preventing stale metadata from leaking between commands.

Compatibility

• Existing callers are unchanged because extra is optional.
• Commands without metadata retain their existing topic and queue behavior.
• Queue processing remains compatible with entries created by the earlier implementation of this branch.

Testing

• Ruby focused suite: 376 examples, 0 failures.
• Python focused suite: 117 tests passed.
• Coverage included the command APIs, scripting wrappers, interface microservices, queue model/processor, command topics, and preidentified protocol framing.
• Verified queued binary metadata round-trips through the COSMOS JSON encoders.
• Ran a Docker-based COSMOS Core end-to-end test using the PR images:
  • submitted a command through the JSON-RPC API with flow_uuid and hv_id metadata;
  • confirmed the interface completed the command write;
  • confirmed both raw and decomposed post-write command topics retained the metadata;
  • confirmed the emitted CCSDS command contained 8 packet bytes with APID 2;
  • confirmed caller-supplied queue_username and approver values were removed.
• git diff --check, Ruby syntax checks, Python compilation, and the repository security/code-analysis checks passed.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud