chore(deps,pytest): update pytest to v8

[danceratopz]

🗒️ Description

Updates to pytest 8.3.5 (from pytest 7.4.4).

TODO

Sanity checks:

• fill
• static fill
• full fixture diff until Prague
• consume direct
• consume rlp
• consume engine
• execute hive
• execute remote
• fix pytest session warning for consume hive: src/pytest_plugins/consume/hive_simulators/conftest.py:152: PytestRemovedIn9Warning: Marks applied to fixtures have no effect

🔗 Related Issues

None

✅ Checklist

• All: Set appropriate labels for the changes.
• All: Considered squashing commits to improve commit history.
• All: Added an entry to CHANGELOG.md.

[marioevz]

I tried to patch the failing function with no success, but I did not spend much time on it.

I think we can gauge how good of an improvement the new pytest version is, and the benefits, and based on that decide to spend enough time and fix the failing static test filling.

[marioevz]

Pushed a fix to static test filling!

It should work up until the latest 8.x.x version :)

[danceratopz]

Verified the fixtures with hasher: All fixtures (including those from static fillers) until Prague match!

Only some test IDs differ, due to a change in how pytest handles duplicate manually specified test IDs. For example, given:

    pytest.param(
        Bytes(b"0x0102030405060708090A0B0C0D0E0F101112131415161718191a1b1c1d1e1f20"),
        id="data_set_1",
    ),
    pytest.param(
        Bytes(b"0x00010203040506000708090A0B0C0D0E0F10111200131415161718191a1b1c1d1e1f"),
        id="data_set_1",
    ),

• pytest 7 produces the IDs:

  test_something[data_set_11]
  test_something[data_set_12]

• pytest 8 produces the IDs:

  test_something[data_set_1_1]
  test_something[data_set_1_2]

This was the case for one of our tests:

tests/berlin/eip2930_access_list/test_tx_intrinsic_gas.py::test_tx_intrinsic_gas

Fixed in dd3ab7f.

[danceratopz]

@marioevz I didn't check execute in "live" mode, otherwise, this LGTM!

[marioevz]

Amazing, thanks for taking care of this!

I think we are closer to updating the minimum python version past the 3.11 ? But that can be a follow up PR.