feat(specs,test-specs,tests): Update Engine API to latest Bogota spec, implement IL inclusion_test

[marioevz]

Description

Follow up to #3373, with the following improvements:

Update to latest Engine API spec

Updates to the latest engine/bogota.md, which includes using engine_newPayloadV6 and engine_forkchoiceUpdatedV5.

Each blockchain engine fixture now contains an inclusionListSatisfied field in each payload with the expected response for the PayloadStatusV2 field from an engine_newPayloadV6 request to a client, and replaces the INCLUSION_LIST_UNSATISFIED payload-status enum value expected in previous fixture formats.

Inclusion List Variant for inclusion_test Marked Tests

All blockchain and state tests from previous forks that were marked in #3337 now automatically generate an inclusion-list variant test where the last transaction of the last block is moved from the block to the inclusion list, with two different expectations:

• If the transaction contained an error, or was otherwise not includable in the block, the block's inclusion list is expected to be validated as satisfied by the client.
• If the transaction contained no errors and was includable in the block, the block's inclusion list is expected to be validated as unsatisfied by the client.

Three bugs were found in the spec with these newly generated tests.

Spec Fixes

Spec bugs caught and fixed by tests mentioned in previous section:

• Transactions with incorrect chain-id were still considered includable
• Transactions with incorrect RLP encoding caused an exception in the inclusion list validator
• Type-3 transactions were considered not-includable by default

Related Issues or PRs

N/A.

Checklist

• Ran fast static checks to avoid CI fails, see Code Standards & Verifying Changes: just static
• PR title has the form <type>(<area>): <title>, where <type> and <area> come from an appropriate C-<type>, respectively A-<area>, label. The title should match the target squash commit message.

Cute Animal Picture

[codecov]

Codecov Report

❌ Patch coverage is 0% with 5 lines in your changes missing coverage. Please review.
⚠️ Please upload report for BASE (eips/amsterdam/eip-7805@aa25eed). Learn more about missing BASE report.

Files with missing lines	Patch %	Lines
src/ethereum/forks/amsterdam/fork.py	0.00%	5 Missing ⚠️

Additional details and impacted files

@@                    Coverage Diff                     @@
##             eips/amsterdam/eip-7805    #3401   +/-   ##
==========================================================
  Coverage                           ?   81.95%           
==========================================================
  Files                              ?      624           
  Lines                              ?    37099           
  Branches                           ?     3397           
==========================================================
  Hits                               ?    30405           
  Misses                             ?     6274           
  Partials                           ?      420           

Flag	Coverage Δ
unittests	81.95% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[spencer-tb]

The t8n requires inclusion lists whenever the spec module tracks inclusion_list_satisfied, and amsterdam shares that module with bogota, so every amsterdam fill crashes.

Fixes for this: spencer-tb/execution-specs@ca86b6e...pr-3401-il-fill-fix, feel free to cherry pick...

What each commit does:

• fixes amsterdam fill CI, spencer-tb@470da9ec70
• inclusionListSatisfied omitted from fixtures on non VALID payloads, match engine api spec, spencer-tb@f7599f602f
• test_collect_only count 3 to 4, CI fix, also in spencer-tb@f7599f602f
• IL variant is generated only for blockchain_test_engine + engine_x, not sync and stateful, spencer-tb@5931b9b5cc
• empty last block and block level only exceptions now fail with a clear "test correctness" error instead of an IndexError, spencer-tb@dd4d467e7b
• decode_transaction no longer crashes the IL validator on empty bytes or first byte 0xff, spencer-tb@c9d3dedd78
• drop the stale "blob transactions are excluded" sentence from the IL check docstring, spencer-tb@aa341bd2ec