Orchestration: optimize timeoutHeight parameter for transactions, queries, and transfers

[0xpatrickdev]

What is the Problem Being Solved?

As an orchestration API developer, I want to make sure we arrive at the correct abstraction and default values for the timeoutHeight: bigint | timeoutTimestamp: bigint parameter required for cross-chain transactions and queries.

The following messages require this parameter, in some form or another, and will default to 0/ 0n if nothing is provided. When the value is 0, it seems this results in an unbound timeout. An unbound timeout can degrade DX + UX.

1. MsgTransfer has timeoutHeight and timeoutTimestamp fields (the generated TS types say both are required, but i think it's actually one or the other)
2. RequestQuery has a height field used for timing out a query
3. TxBody has a timeoutHeight field used for timing out a tx message

Description of the Design

1. Need to determine if its's the orchestration API's responsibility to set a default timeout value, or it's something passed down to users
2. Need to determine if revisionHeight is something ChainInfo can reliably provide
3. Need to determine what sensible defaults values should be for example contracts and documentation (+ orchestration service depending on the answer to 1)

Security Considerations

Scaling Considerations

Test Plan

Upgrade Considerations