Fix multiple ZK integration issues: domain sep, schema parity, addres…

[soomtochukwu]

…s binding

Wave Ticket

Wave Issue Key: ZK-011, ZK-071, ZK-072, ZK-073

Linked issue:

• Closes ZK-011: Add explicit domain separation tags to note commitments #255
• Closes ZK-071: Split the withdrawal circuit schema from the contract verifier payload explicitly #347
• Closes ZK-072: Replace lossy recipient decoding with a verifiable address-binding strategy #348
• Closes ZK-073: Redesign relayer binding and zero-relayer semantics across SDK and contract code #349

What Changed

• ZK-011: Add explicit domain separation tags to note commitments #255 (ZK-011): Added COMMITMENT_DOMAIN_SEP and updated compute_commitment in circuits and SDK to include domain separation tag and denomination for proper hash distinctness.
• ZK-071: Split the withdrawal circuit schema from the contract verifier payload explicitly #347 (ZK-071): Fixed Public Input Schema parity by dynamically assembling pool_id and denomination on the smart contract side and reducing the submitted ZK proof payload down to the expected 6 fields.
• ZK-072: Replace lossy recipient decoding with a verifiable address-binding strategy #348 (ZK-072): Replaced the "lossy" address decoding with a cryptographic address hashing validation. execute now takes recipient_address directly and checks it against the public input recipient hash.
• ZK-073: Redesign relayer binding and zero-relayer semantics across SDK and contract code #349 (ZK-073): Updated relayer binding logic to clearly enforce STELLAR_ZERO_ACCOUNT sentinel behaviors when an optional relayer isn't passed in.
• Ignore: Add test_snapshots and target to .gitignore.

Note: The current implementation has been successfully tested on the contract side and all Rust/Soroban unit tests pass properly (21/21 ok). We have noticed that running the SDK test suite via Jest generates roughly 43 test failures; however, after cross-validating the main branch, we identified that these same Jest/TS failures were already present upstream before applying our modifications and are completely unrelated to these ZK ticket resolution logic changes.

Validation

• I linked the ZK ticket keys above.
• I ran the derived checks locally for the ticket I am implementing.
• I updated tests or fixtures when the ticket changed circuit or witness behavior.

Wave Ticket

Wave Issue Key: ZK-___

Linked issue:

• Closes #

What Changed

Validation

• I linked the ZK ticket key above.
• I ran node scripts/zk_ticket_check.mjs --issue-key ZK-___.
• I ran the derived checks locally for the ticket I am implementing.
• I updated tests or fixtures when the ticket changed circuit or witness behavior.

Validation output:

paste the command output here