It's happening because of this line:

When removing it and running tests with --isolate as default, there is a falining test can_deploy_with_create2. It's failing because for scripts we are simply changing caller of CREATE2 deployment to DEFAULT_CREATE2_DEPLOYER if it should be broadcasted. That way, because of non-zero gas price in forking environment, revm expects create2 deployer to have enough funds to pay gas * gas_price

So we can either prefund create2 deployer along with caller when initializing test/script runner, or prefund it at apply_create2_deployer (https://github.com/foundry-rs/foundry/blob/master/crates/cheatcodes/src/inspector.rs#L1432) when it's actually being used

It is also worth noting that removing gas price overwriting might break some tests

Right now it is possible to do something like this:

vm.txGasPrice(1); // basically anything non-zero
vm.startPrank(ALICE); // prank address with zero balance
someContract.someMethod();

call to someContract will revert in isolation because revm expects ALICE to have enough funds to pay for gas

cc @mattsse @onbjerg

confirming still reproducible with latest version