fix(cli): cannot build on Cannon network with --dry-run

[saeta-eth]

Running cannon build with --dry-run without specifying the --chain-id should throw an error.

Bug:

cannon build mintable-token.cannonfile.toml --dry-run
Building the foundry project...
forge build succeeded

Anvil instance running on: http://127.0.0.1:61073

shutting down existing anvil subprocess 24191
/usr/local/lib/node_modules/@usecannon/cli/dist/src/rpc.js:69
        throw new Error('Cannot set both an anvil forkUrl and a proxy provider connection');
              ^

Error: Cannot set both an anvil forkUrl and a proxy provider connection
    at runRpc (/usr/local/lib/node_modules/@usecannon/cli/dist/src/rpc.js:69:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async ChildProcess.<anonymous> (/usr/local/lib/node_modules/@usecannon/cli/dist/src/rpc.js:81:25)

Node.js v20.16.0

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 290b461e4a7255b52d929c50a3e17ad63381b45d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR