`<expectRevert>` check fails if `0` address is called

The following test fails when analyzed with kontrol prove:

 function test_proveWithdrawalTransaction_calldata()
        external
    {
        testedContract = TestedContract(payable(address(0)));

        vm.expectRevert();
        testedContract.functionName();
    }
}

The call to functionName is expected to revert due to a failed EXTCODESIZE check on testedContract, however, the test is failing despite vm.expectRevert();.

It's probably caused by the fact that the failing check happens before the CALL opcode, but we should investigate and compare it with Foundry's behavior.

Start with test_proveWithdrawalTransaction_calldata and reproduce the failure with kontrol prove, focusing on the call to testedContract.functionName() after vm.expectRevert(). Compare this behavior with Foundry's handling of a zero-address call and determine whether the EXTCODESIZE failure before CALL should satisfy the expected revert; done means the behavior is investigated and aligned or clearly documented.