test(a3p): move localchain test to upgrade-next (#9467)

## Description

`init-localchain` is run in the upgrade handler so the test of it
belongs in the same (upgrade) proposal.

### Security Considerations

<!-- Does this change introduce new assumptions or dependencies that, if
violated, could introduce security vulnerabilities? How does this PR
change the boundaries between mutually-suspicious components? What new
authorities are introduced by this change, perhaps by new API calls?
-->

### Scaling Considerations

<!-- Does this change require or encourage significant increase in
consumption of CPU cycles, RAM, on-chain storage, message exchanges, or
other scarce resources? If so, can that be prevented or mitigated? -->

### Documentation Considerations

<!-- Give our docs folks some hints about what needs to be described to
downstream users.

Backwards compatibility: what happens to existing data or deployments
when this code is shipped? Do we need to instruct users to do something
to upgrade their saved data? If there is no upgrade path possible, how
bad will that be for users?

-->

### Testing Considerations

<!-- Every PR should of course come with tests of its own functionality.
What additional tests are still needed beyond those unit tests? How does
this affect CI, other test automation, or the testnet?
-->

### Upgrade Considerations

<!-- What aspects of this PR are relevant to upgrading live production
systems, and how should they be addressed? -->

a3p-integration/proposals/b:localchain/localchain.test.js → a3p-integration/proposals/a:upgrade-next/localchain.test.js

@@ -1,7 +1,8 @@
-/* eslint-disable @jessie.js/safe-await-separator */
 import test from 'ava';
 
-import { agd, waitForBlock } from '@agoric/synthetic-chain';
+import { agd, evalBundles, waitForBlock } from '@agoric/synthetic-chain';
+
+const SUBMISSION_DIR = 'localchaintest-submission';
 
 const readPublished = async path => {
   const { value } = await agd.query(
@@ -18,7 +19,11 @@ const readPublished = async path => {
   return obj.values[0];
 };
 
+// The testing assertions are in the submission that runs in the core-eval.
+// The test here runs that and confirms the eval made it through all the assertions.
 test(`localchain passes tests`, async t => {
+  await evalBundles(SUBMISSION_DIR);
+
   const nodePath = 'test.localchain';
   const nodeValue = JSON.stringify({ success: true });
 

a3p-integration/proposals/a:upgrade-next/package.json

@@ -7,7 +7,8 @@
       "coreProposals": []
     },
     "sdk-generate": [
-      "vats/probe-zcf-bundle.js probe-submission"
+      "vats/probe-zcf-bundle.js probe-submission",
+      "vats/test-localchain.js localchaintest-submission"
     ],
     "type": "Software Upgrade Proposal"
   },