acceptance test of bids surviving upgrades

[turadg]

What is the Problem Being Solved?

We have some tests of bids surviving restarts but we don't have any chain integration tests of it.

Today we encountered the following error while qualifying upgrade-17 with Mainfork,

SwingSet: xsnap: v10: UnhandledPromiseRejectionWarning: { incarnationNumber: 3, name: 'vatUpgraded', upgradeMessage: 'vat upgraded' }

and it took some debugging to identify it as the watcher for outstanding bids. If the A3P tests had that in their logs it would be more apparent as part of the expected behavior. (Better error handling may be in order but that requires upgrading vat-bridge which is way off.)

Description of the Design

Place a bid in some "use" layer of some early proposal.

In z:acceptance make sure it's still live.

Perhaps also adjust prices so that the bid is fulfilled and confirm payouts.

Security Considerations

Scaling Considerations

Test Plan

Upgrade Considerations

[mhofman]

Better error handling may be in order but that requires upgrading vat-bridge which is way off

Having the smart wallet use a vow as result of the bridge handler would likely be the best approach. Then we have more plumbing in the bridge vat to bubble that up to cosmic-swingset and vstorage. See #8441