feat(provisionPool): allow overriding PerAccountInitialAmount during contract upgrade

[Jorge-Lopes]

closes: #10562

Description

This PR updates the provisionPool contract to allow overriding the PerAccountInitialAmount parameter, which is governed by the Economic Committee during contract upgrades.

To achieve the above functionality, this PR introduces the following changes:

• The PerAccountInitialAmount is now injected to the contract through privateArgs instead of terms.
• Use the makeParamManagerFromTerms method from the governance package to manage the PerAccountInitialAmount values during upgrades.
• Updated the public and creator facets to handle the replace handleParamGovernance with makeParamManagerFromTerms.

The core-eval proposal used to upgrade provisionPool was also updated to fetch the current value of PerAccountInitialAmount set on Vstorage and include it on the new privateArgs

Security Considerations

The changes introduced in this PR modifies the provisionPool publicFacet, which no longer exposes all method declared in the publicMixinAPI methodGuard, more specifically, those declared in typedAccessors.
My analysis indicates that these methods are not utilized by any contract consuming the provisionPool publicFacet, which is why they were omitted.

However, if this analysis overlooked any instances where the removed methods are in use, their absence could introduce vulnerabilities.

Scaling Considerations

Documentation Considerations

Testing Considerations

The existing unit tests for the inter-protocol and vats packages, as well as the a3p-integration tests have been verified to continue passing with these changes.

Additionally, these changes were tested against the governance acceptance tests in the a3p-integration which ensures that governed parameter values remain intact after a contract upgrade.
To maintain the scope of this PR, that specific test is not included here. However, it will be introduced in PR #10555, which is planned to be opened once this change is merged.

Upgrade Considerations

[cloudflare-workers-and-pages]

Deploying agoric-sdk with    Cloudflare Pages

Latest commit:	197aa4b
Status:	🚫  Build failed.

View logs

[Jorge-Lopes]

@Chris-Hibbert, after I had already assigned you as the reviewer, I noticed some unexpected CI failures in this PR. I'll investigate the root cause of these issues first thing tomorrow morning.