fix(cli): add pytest EIP markers for valid_from tests

[shrirajpawar4]

🗒️ Description

Auto-add plain pytest EIP#### markers for tests that are explicitly enabled by valid_from("EIP####").

This makes EIP-scoped selection work as requested in #2675, so commands like:

uv run fill --clean --fork=Amsterdam -m EIP7928

can select tests that are marked valid from a given EIP without relying on ad hoc -k expressions.

This change is intentionally narrow:

• It promotes explicit valid_from("EIP####") markers into plain pytest markers during collection.
• It does not treat negative selectors such as valid_before("EIP####") as matching -m EIP####.
• It registers known EIP#### markers so they are valid pytest markers.

It also adds targeted regression tests covering:

• function-level valid_from("EIP####")
• param-level valid_from("EIP####")
• the negative case where valid_before("EIP####") must not match -m EIP####

🔗 Related Issues or PRs

Fixes #2675.

✅ Checklist

• All: Ran fast static checks to avoid unnecessary CI fails, see also Code Standards (https://eest.ethereum.org/main/getting_started/code_standards/) and Enabling Pre-commit Checks
  (https://eest.ethereum.org/main/dev/precommit/):

  just static

• All: PR title adheres to the repo standard (https://eest.ethereum.org/main/getting_started/contributing/?h=contri#commit-messages-issue-and-pr-titles) - it will be used as the squash commit mes
  sage and should start type(scope):.

• All: Considered updating the online docs in the /ethereum/execution-specs/blob/HEAD/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 (https://eest.ethereum.org/main/tests/) are correctly formatted.

• Tests: For PRs implementing a missed test case, update the /ethereum/execution-specs/blob/HEAD/docs/writing_tests/post_mortems.md to add an entry the list.

• Ported Tests: All converted JSON/YML tests from /ethereum/tests or /ethereum/execution-specs/blob/HEAD/tests/static have been assigned @ported_from marker.

Verification

Manual behavior check against a real test file:

  uv run pytest \
    -c packages/testing/src/execution_testing/cli/pytest_commands/pytest_ini_files/pytest-fill.ini \
    tests/frontier/validation/test_header.py \
    --until=Amsterdam \
    --collect-only -q -m EIP7928

Observed result:

• collected test_gas_limit_below_minimum[...,gas_limit_5000_1]
• did not collect ...,gas_limit_5000_0

This confirms -m EIP7928 selects the valid_from("EIP7928") case and not the valid_before("EIP7928") case.

Targeted regression tests:

  uv run pytest \
    packages/testing/src/execution_testing/cli/pytest_commands/plugins/forks/tests/test_markers.py \
    -q \
    -k 'function_level_valid_from_eip_is_selectable_by_mark or param_level_valid_from_eip_is_selectable_by_mark or negative_eip_selectors_do_not_add_eip_markers'

Observed result:

3 passed

Cute Animal Picture

[shrirajpawar4]

@fselmo do take a look at PR whenever you can sir