Move the Zoe contract files out of packages/zoe

[katelynsills]

The Zoe contract files should be in a different package. Zoe is deep, crucial infrastructure. CoveredCall is a cool example.

This will help us test the code coverage of Zoe specifically, versus the contracts.

Having an aggregate package for examples (other than Multipool Autoswap) seems reasonable rather than exploding them into unmotivated individual packages. Separating out individual examples into their own packages can wait.

Chores:
Create a new package, called something like @agoric/sample-contracts (name TBD)
Create a new package specifically for multipool autoswap (name TBD)

[Tartuffo]

@dckc This does not have an area label that is covered by our weekly tech / planning meetings. Can you assign the proper label? We cover: agd, agoric-cosmos, amm, core economy, cosmic-swingset, endo, getrun, governance, installation-bundling, metering, run-protocol, staking, swingset, swingset-runner, token economy, wallet, zoe contract. Or, if this is accurately labeled by an area label we should be covering in one of our weekly meetings, please LMK.

[dckc]

The Zoe label should fit in the Zoe/ERTP meeting.

[Tartuffo]

Yeah, I realized we do cover "zoe" label in the meeting. Sorry.

[Tartuffo]

@dckc Can you please put an estimate on this?

[dckc]

It's already estimated at 3... that seems about right given risks of unknowns, but I suppose the work that I know needs doing is more of a 2.