feat!: contract registers chains given in terms

[dckc]

closes #52

• [x] parameterize the core-eval according to runtime environment, like revise-chain-info.builder.js in multichain-testing
• [x] refactor makeAgd usage so that caller arranges for kubectl a la dockerExec
• [x] relax agd.query() type to allow query ibc ...
• figure out type errors related to the terms: test/orca-contract.test.js:334:9 - error TS2322: Type 'Record<string, ChainInfo>' is not assignable to type 'never'.
  • punted with @ts-expect-error
• [x] starship testing in ci

Testing

• unit tests for new feature, plus refactors and problems found along the way
• restore multi-chain starship integration-testing in ci

cc @Jovonni @samsiegart @LuqiPan

[dckc]

@turadg please take another look.

The version you approved would have been a regression. I hadn't tested deploying it to a running chain. I extended this to do that in ci, based on ...

• 50

[dckc]

@turadg a diff from what you approved to the corresponding commit now might be helpful. Then all the commits after 19ebfe0b206cf1acab2e08f8364e24ac83e1fd40 are new since your review.