fix: When setting a new zcfBundleCap, store it in baggage

[Chris-Hibbert]

closes: #8805

Description

While reviewing a PR to push code to a release branch, @erights noticed that we don't save new zcfBundleCaps persistently.

Security Considerations

None

Scaling Considerations

None

Documentation Considerations

None.

Testing Considerations

As we're testing zoe upgrades in a3p, we'll verify that the newly set value survives zoe upgrade.

Upgrade Considerations

It's all about upgrade.

This will be immediately copied to a release staging branch to be included when we upgrade Zoe.

[erights]

I notice that saveBundleCap does an init. Thus, it should be called at most once. (Given its purpose, more like exactly once.) Skimming the code around this change, I was not able to convince myself it could not be called multiple times. I don't understand the interlock

  const setVatAdminService = Far('setVatAdminService', lateVatAdminSvc => {
    vatAdminSvc = lateVatAdminSvc;
    saveBundleCap();
  });

  if (vatAdminSvc) {
    saveBundleCap();
  } else if (zoeBaggage.has('zcfBundleCap')) {
    zcfBundleCap = zoeBaggage.get('zcfBundleCap');
    // in this case, it'll be known to have been resolved, but that's fine
    vatAdminSvc = zoeBaggage.get('vatAdminSvc');
  }

[Chris-Hibbert]

I was not able to convince myself it could not be called multiple times.

I changed it check if init has already been called, and call set() in that case.

[erights]

LGTM, thanks!