chore: more fixes for --all-features tests

[grandizzy]

Motivation

more fixes for cargo test --all --all-features clean run

• send shutdown signal for long running tests that spawns anvil, fixing

failed to spawn node: Os { code: 98, kind: AddrInUse, message: "Address already in use" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

• avoid RPC URL rate limit for storage test
• avoid etherscan rate limit for verify_bytecode tests, fixing

Error: 
Received error response: status=0,message=NOTOK, result=Some("Max calls per sec rate limit reached (5/sec)")
failures:
    verify_bytecode::can_verify_bytecode_with_metadata

• remove DAPP_REMAPPINGS env var from can_override_config test, fixing

thread 'config::can_override_config' panicked at crates/forge/tests/cli/config.rs:210:5:
assertion failed: `(left == right)`'
  left: `"ds-test/=/tmp/can_override_config-68Zsmm2o/lib/forge-std/lib/ds-test/from-env/"`
 right: `"ds-test/=/tmp/can_override_config-68Zsmm2o/lib/forge-std/lib/ds-test/from-file/"`

Differences (-left|+right):
-ds-test/=/tmp/can_override_config-68Zsmm2o/lib/forge-std/lib/ds-test/from-env/
+ds-test/=/tmp/can_override_config-68Zsmm2o/lib/forge-std/lib/ds-test/from-file/

Solution

[mattsse]

I see, that makes sense

one suggestion

[mattsse]

could we convert this to a function on handle?

and document why we call this for some tests

[DaniPopes]

we should just not be using env vars in cli tests, it can only work if its set on a spawned command

[grandizzy]

yeah, will clean those tests and move such remapping test in dedicated