test stATOM proposal in CI using an upgrade test

[turadg]

What is the Problem Being Solved?

The community's stATOM proposal will be tested elsewhere but we're not confident telling the community it's ready until the testing is automated.

Moreover, if we don't include it in the upgrade tests then they will drift from Mainnet. E.g. what is vaultFactory.managers.manager1

Description of the Design

Add the proposal to a deployment upgrade test

The addBrand call should wait for the auction to complete. That signal comes from a subscriber, which should be careful to stop subscribing.

Security Considerations

Scaling Considerations

Test Plan

Auctions continue to work for both. See also #8270

Upgrade Considerations

Tasks

Preview Give feedback

1. addAssetToVault does not support initial lower-case asset names #8235
   Inter-protocol bug +2
   
2. timing work-around for stATOM proposal #8347
   enhancement +1
   
3. build and tests proposals by stages agoric-3-proposals#4
   +0
4. test adding stATOM collateral by fetching proposer's bundles #8454
   +0
5. base upgrade tests on agoric-3-proposals #8476
   automerge:rebase bypass:integration +2

[dckc]

includes adding code to handle timing constraints to avoid #8296, #8307
per meeting with @turadg and co

Without a fix, it's crucial that the oracle be started before the auction, and that the new brand is added to the auction after an auction round ends and before the next one starts.

[dckc]

fixed in Agoric/agoric-3-proposals#4