Build fastUsdc core-eval and confirm it can be deployed separate from an upgrade

[turadg]

No description provided.

[dckc]

Clarify how this is different from what we're doing in multichain-testing?

agoric-sdk/multichain-testing/test/fast-usdc/fast-usdc.test.ts

Lines 37 to 38 in f0ccde6

	const contractBuilder =
	'../packages/builders/scripts/fast-usdc/start-fast-usdc.build.js';

agoric-sdk/multichain-testing/test/support.ts

Lines 129 to 132 in f0ccde6

	t.log('bundle and install contract', contractName);
	await deployBuilder(contractBuilder, builderOpts);
	await retryUntilCondition(
	() => vstorageClient.queryData(`published.agoricNames.instance`),

[LuqiPan]

@dckc will upload the bundle on mainnet

[dckc]

I verified that the bundle can be installed on mainnet: tx D34FD3....

The bundle comes from the a3p-integration artifact of a recent ci run:

   {
      entrypoint: '@agoric/fast-usdc/src/fast-usdc.contract.js',
      bundleID: 'b1-82b81cbbdc0399a60665dd383ce3755214474cdda144e74a631dc98d23c9f8974f2a5a154977c88f8ce82e069f38ea0b67451558d70c45fa10f393d409fbe5b4',
    },

Previous to uploading it, I adapted a bundle-size test from dapp-agoric-basics:

• test(fast-usdc): bundle size under 1MB RPC limit #10902

It's not ready to merge, but "Without merging, this PR serves to show the bundle is small enough."

[turadg]

For future reference, the a3p proposal test is our best way to confirm that the proposal can succeed it applying on Mainnet.