PFM transfer covering remote chain A's view of remote B's denoms

[turadg]

What is the Problem Being Solved?

Per @0xpatrickdev , we need and don't have any test scenarios for building PFM messages which require us to know RemoteChainA's view of RemoteChainB's denoms.

Description of the Design

#9491 made progress in pursuit of,

• orchestration: example dapp contract that can swap on osmosis #8863

However this is smaller in scope. The scope of this is testing PFM and the pfm memo. (Perhaps through sendAnywhere contract)

Additional discussion

Tasks

Beta Give feedback

1. feat: CosmosChainInfo includes pfmEnabled: bool #10329
   force:integration +1
   
2. implementation and test for COA
3. local-orchestration-account: transfer supports multi-hop pfm routes #10445
   enhancement +1
   

Security Considerations

Scaling Considerations

Test Plan

Upgrade Considerations

[dckc]

A relevant detail: "chain A's view of remote B's denoms" is supposed to be called getLocalDenom as in chainA.getLocalDenom(chainBdenom), according to July 31 discussion #9814 (comment) where we dug up earlier API drafts.

A WIP version is included in

• feat!: makeOsmosisSwap() using getDenomOn #9814