avoid custom core-eval for contract deployment

[dckc]

sketch:

in fun1.contract.js:

export meta = {
  privateArgsShape: {
    storageNode: M.remote('published.fun1'); // or perhaps...
    storage: M.remote('StorageNode: published.fun1')
  }
}

a deploy-contract.js tool imports the contract, checks the meta, and builds core-eval code to fulfill it, either open-coded or by giving some data to an interpreter.

Some prototyping experience is available in...

• contractStarter.js

refs:

• how to limit excess authority when registering a storage node #8594
• how to grant limited authority to save contract upgrade materials? #8378

cc @Jovonni

[turadg]

#9472 has an idea I played with to automate some naming

[dckc]

on July 17 , @Jovonni and I started experimenting...

• feat: deploy contract without custom code (WIP) dapp-agoric-basics#48

[dckc]

One of my experiments in this area was blocked back on Sep 12. A PR just landed that addresses that issue.

[dckc]

a few weeks ago, I had another brainstorm:

• SPIKE: factor out Orch contract core-eval boilerplate #10695

Drive most of the core-eval code from ContractMeta and permit.

I'm not quite happy with where it ended up, but I think the general approach has promise.

cc @amessbee @anilhelvaci