build SDK releases from master

[turadg]

What is the Problem Being Solved?

Currently we have a branch for each release of SDK. E.g.

• https://github.com/Agoric/agoric-sdk/tree/dev-upgrade-13
• https://github.com/Agoric/agoric-sdk/tree/dev-upgrade-14
• https://github.com/Agoric/agoric-sdk/tree/dev-upgrade-15

This approach requires painstaking cherry picking and has been the source of some confusion.

Description of the Design

Make it safe to cut releases from master. This will require at least,

### Tasks
- [ ] #8961 
- [ ] #8219 
- [ ] upgrade all vats
- [ ] https://github.com/Agoric/agoric-sdk/issues/9417

Security Considerations

Scaling Considerations

Test Plan

Upgrade Considerations

[Chris-Hibbert]

In Slack, @mhofman said

the prerequisite to releasing from master is roughly that all vats are upgradable and upgraded, or that the code for non upgradable vats is functionally equivalent in master

[dckc]

oops... wrong ticket. moving to #9417 (comment)

looks like as of upgrade-16, we're still doing opt-in:

• Cherry-pick upgrade-16 commits #9545
• Upgrade-16 cherry-picks round 2 #9625
• Upgrade-16 cherry-picks round 3 #9640
• chore: More upgrade-16 cherry-picks #9675
  plus
• fix(cosmos): don't rerun store migrations on upgrade #9683

this is based on looking at git log --graph --oneline origin/master origin/dev-upgrade-16
with master = 3c66f4b and dev-upgrade-16 = 0df76a7

[Chris-Hibbert]

coreEval agoric-upgrade-16av was built from a commit on master.