ChainHub method should be sync

[0xpatrickdev]

What is the Problem Being Solved?

ChainHub contains a mixture of synchronous and asynchronous calls. All calls should be synchronous, see https://codecider-app.vercel.app/d/6fb8c4f7-1465-4b19-8d85-2326e29d8ffc/view#?!-what-chainhub-methods-should-be-async

Description of the Design

• getChain() should be synchronous and no longer fallback to an agoricNames lookup
• getConnectionInfo() should be synchronous and no longer fallback to an agoricNames lookup
• getChainsAndConnection() should be synchronous and no longer fallback to an agoricNames lookup

Note: this requires contract authors to seed their chainHub at contract start time. With #10571 and #10329, orchestration example contracts + FUSDC all already do this.

Security Considerations

Scaling Considerations

Test Plan

Upgrade Considerations