fix: skip storage verification for empty storage dict

[mandeepmourya007]

Closes #2162

Account(storage={}) caused infinite loop when verifying storage over RPC (attempting to check 2^256 keys). Skip storage check when no keys are specified - empty storage dict is now treated as 'allow any storage values'.

🗒️ Description

🔗 Related Issues or PRs

N/A.

✅ Checklist

• All: Ran fast tox checks to avoid unnecessary CI fails, see also Code Standards and Enabling Pre-commit Checks:

  uvx tox -e static

• All: PR title adheres to the repo standard - it will be used as the squash commit message and should start type(scope):.
• All: Considered updating the online docs in the ./docs/ directory.
• All: Set appropriate labels for the changes (only maintainers can apply labels).
• Tests: Ran mkdocs serve locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.
• Tests: For PRs implementing a missed test case, update the post-mortem document to add an entry the list.
• Ported Tests: All converted JSON/YML tests from ethereum/tests or tests/static have been assigned @ported_from marker.

[marioevz]

This change is modifying the behavior that a lot of tests expect.

We need to:

1. Define a new sentinel value Storage.EMPTY (perhaps simply equal to None) that is used to signal that the test expects the storage to be completely empty.
2. Go through all tests that are currently doing Account(storage={}) and use the sentinel value instead, to make sure that the checks remain the same for these tests
3. Modify TransactionPost to handle the sentinel value in the way that the original issue describes (Using eth_getProof for example).

[mandeepmourya007]

This change is modifying the behavior that a lot of tests expect.

We need to:

1. Define a new sentinel value Storage.EMPTY (perhaps simply equal to None) that is used to signal that the test expects the storage to be completely empty.
2. Go through all tests that are currently doing Account(storage={}) and use the sentinel value instead, to make sure that the checks remain the same for these tests
3. Modify TransactionPost to handle the sentinel value in the way that the original issue describes (Using eth_getProof for example).

@marioevz please check i update PR but not sure why my old commit lost

[marioevz]

This change is modifying the behavior that a lot of tests expect.
We need to:

1. Define a new sentinel value Storage.EMPTY (perhaps simply equal to None) that is used to signal that the test expects the storage to be completely empty.
2. Go through all tests that are currently doing Account(storage={}) and use the sentinel value instead, to make sure that the checks remain the same for these tests
3. Modify TransactionPost to handle the sentinel value in the way that the original issue describes (Using eth_getProof for example).

@marioevz please check i update PR but not sure why my old commit lost

Thanks, I see the changes and looks very good so far!

One missing thing though is that we need to search for tests doing post = Account(..., storage={}, ...) because this PR changes the meaning of this, and most of the tests should be updated to now do post = Account(..., storage=Storage.EMPTY, ...), otherwise we are going to skip checks on those tests that currently expect the storage to be empty.

[mandeepmourya007]

This change is modifying the behavior that a lot of tests expect.
We need to:

1. Define a new sentinel value Storage.EMPTY (perhaps simply equal to None) that is used to signal that the test expects the storage to be completely empty.
2. Go through all tests that are currently doing Account(storage={}) and use the sentinel value instead, to make sure that the checks remain the same for these tests
3. Modify TransactionPost to handle the sentinel value in the way that the original issue describes (Using eth_getProof for example).

@marioevz please check i update PR but not sure why my old commit lost

Thanks, I see the changes and looks very good so far!

One missing thing though is that we need to search for tests doing post = Account(..., storage={}, ...) because this PR changes the meaning of this, and most of the tests should be updated to now do post = Account(..., storage=Storage.EMPTY, ...), otherwise we are going to skip checks on those tests that currently expect the storage to be empty.

please have a look I updated other test cases