test(a3p-integration): Update "swap into IST" to force the default gas limit

[gibson042]

Description

Extracted from #10165 and extends #10447.

• chore(a3p-integration): Increase the verbosity of psmSwap
• feat(agoric-cli): Block agoric wallet send on tx inclusion (-bblock)
• test(a3p-integration): Update "swap into IST" to force the default gas limit
• feat(agoric-cli): Add agoric wallet send gas limit options (defaulting to --gas=auto)

Security Considerations

None known.

Scaling Considerations

None known.

Documentation Considerations

The CLI is self-documenting:

$ agoric wallet send --help
Usage: agoric wallet send [options]

send a prepared offer

Options:
  --home <dir>                      agd application home directory
  --keyring-backend <os|file|test>  keyring's backend (os|file|test) (default "os")
  --from [address]                  address literal or name
  --offer [filename]                path to file with prepared offer
  --dry-run                         spit out the command instead of running it
  --gas                             gas limit; "auto" [default] to calculate automatically
  --gas-adjustment                  factor by which to multiply the limit calculated from
                                    --gas=auto [default 1]
  --verbose                         print command output
  -h, --help                        display help for command

Testing Considerations

The new --gas=auto default is used every except "swap into IST", which is now explicitly responsible for covering the "default gas with automatic wallet provisioning" scenario.

Upgrade Considerations

This will now detect any future change that pushes PSM swap gas consumption beyond the default limit.

[turadg]

I'm reluctant to make a new API for what Execa offers. Can you make the case for this? (Or convert to use Execa?)

Execa has ambient authority, but I think that's acceptable in testing libs. Pretty sure that's in our guidelines.

[gibson042]

Yeah, it looks like execa can handle everything we care about. I'll see about refactoring on top of it after CI passes with this.

[cloudflare-workers-and-pages]

Deploying agoric-sdk with    Cloudflare Pages

Latest commit:	58272b4
Status:	✅  Deploy successful!
Preview URL:	https://6a291a1e.agoric-sdk.pages.dev
Branch Preview URL:	https://gibson-2024-11-cli-gas-estim.agoric-sdk.pages.dev

View logs

[turadg]

I have some requests but not blocking since you're just merging this into the base.

I'm fine reviewing the base after this is in there. If you land the base and this goes on top of master instead, please address before merge.

[turadg]

why the dots? If it's for grouping, I think comment lines would be clearer

Suggested change

	...[`--node=${rpcAddrs[0]}`, `--chain-id=${chainName}`],
	...[`--keyring-backend=test`, `--from=${address}`],
	...['tx', 'swingset', 'wallet-action', '--allow-spend', offer],
	...['-ojson', '-bblock'],
	// chain
	`--node=${rpcAddrs[0]}`, `--chain-id=${chainName}`,
	// account
	`--keyring-backend=test`, `--from=${address}`,
	// transaction
	'tx', 'swingset', 'wallet-action', '--allow-spend', offer,
	// output
	'-ojson', '-bblock',

[gibson042]

Updated to use concat in alignment with execSwingsetTransaction. The above style doesn't work because our lint configuration prohibits array literals in which some but not all elements share a line.