Fix token pool LQT release verification

[KevinMehrabi]

Summary

• Decode the token pool's optional LQT address before comparing it with the release receipt.
• Recheck the exact LQT link during the paused final-handoff gate.
• Add regression coverage for Taquito's { Some: address } representation and mismatched links.

Reason

The fresh Shadownet rehearsal of merged commit e9cc252 exposed a release-tooling mismatch: the on-chain LQT address and receipt were identical, but the live invariant verifier stringified the decoded option object and rejected the valid deployment.

Validation

• npm run typecheck
• npm test: 68 passing
• Corrected signer-free live invariant verification passed against the fresh USDt-tzBTC Shadownet deployment after swaps in both directions, add/remove liquidity, fee claims, pause rejection, and unpause.

This changes release verification only; it does not change the pool or LQT contract artifacts.