Update Token Standard HTTP handler to support locks

Problem

The getTransferInstructionChoiceContextV1 method in HttpTokenStandardTransferInstructionHandler only fetches choice contexts for AmuletTransferInstruction at the moment, but the transferInstructionId may now represent a GovernanceLock or VestingLock.

Acceptance Criteria

Passing integration test for full happy path flow; covers GovernanceLock/VestingLock creation and management.

Budget

3 days

Solution

Update getTransferInstructionChoiceContextV1 to fall back to looking up GovernanceLock and VestingLock.

Risk Mitigation

• Depends on #7124; integration test requires ingestion of contracts in order to pass

Exclusions

• DAR bump and DarResources regeneration, though note that CI won’t pass without this
• The fallback approach requires 2 DB queries for GovernanceLocks and 3 queries for VestingLocks. An alternate, more performant approach would look up a generic contract by the given transferInstructionId, then match on its type. This type of generic contract lookup does not exist and addition of it is out of scope for now.