chore: implement parseInboundTransfer

[anilhelvaci]

closes: #11374

Description

This PR implements the design described at #11374. The need for such a design is surfaced during when we tried to handle any denom incoming to a contract's address hook. We are trying to unblock that functionality with this solution.

Security Considerations

None.

Scaling Considerations

No concerns about this.

Documentation Considerations

None.

Testing Considerations

We some unit tests that showcases this method's functionality. Ideally there should also be multichain test where a contract uses this method to make sense out of some incoming IBC transfer in its address hook. We do have an on-going effort for that. See #11304

Upgrade Considerations

None.

[anilhelvaci]

I moved parseInboundTransfer type definition from OrchestrationAccountCommon to LocalAccountMethods like below. FYI @michaelfig

agoric-sdk/packages/orchestration/src/cosmos-api.ts

Lines 363 to 368 in 469fc10

	parseInboundTransfer: (packet: Record<string, any>) => Promise<{
	amount: DenomAmount;
	fromAccount: AccountId;
	toAccount: AccountId;
	extra: Record<string, any>;
	}>;

[cloudflare-workers-and-pages]

Deploying agoric-sdk with    Cloudflare Pages

Latest commit:	8757717
Status:	✅  Deploy successful!
Preview URL:	https://589fc85f.agoric-sdk.pages.dev
Branch Preview URL:	https://anil-11374-parse-inbound.agoric-sdk.pages.dev

View logs

[michaelfig]

Great work! LGTM.