feat(fill): pass blobSchedule into t8n binary

[pdobacz]

🗒️ Description

The blobSchedule.json is required by evmone-t8n tool now, in order to fill tests correctly. We add a new structure intended to be used as a JSON generator for the filesystem evaluation inputs - I guess trying to mimic what TransitionToolRequest does, lmk if I misread the idea here.

Appropriate change on the evmone end: ipsilon/evmone#1330

🔗 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 --with=tox-uv tox -e lint,typecheck,spellcheck,markdownlint

• All: PR title adheres to the repo standard - it will be used as the squash commit message and should start type(scope):.
• All: Considered adding an entry to CHANGELOG.md.
• All: Considered updating the online docs in the ./docs/ directory.
• All: Set appropriate labels for the changes (only maintainers can apply labels).

[pdobacz]

coverted to draft b/c maybe we should send more in that JSON (to include network and (future) ...Time fields to be able to t8n in e.g. BPO1)

[pdobacz]

Ready to review. The version pushed now will process (in line with ipsilon/evmone#1330) an --input.config argument and JSON, so that end-game schedule (with ...Time) fields is support-able, doesn't worry about handling fill --fork OsakaToBPO1AtTime15k, for now. AFAIK this doesn't break any existing fill-capabilities of evmone, so we can maybe think about providing them as a 2nd step

[marioevz]

Thanks for implementing this, some comments.

[marioevz]

This one is very similar to the already-existing TransitionToolContext, so we can just repurpose that one instead.

[marioevz]

As discussed in chat group, let's pass instead:

Suggested change

	blob_schedule: BlobSchedule
	blob_params: BlobParams

Also, we already have a definition that fits our needs in here:

execution-spec-tests/src/ethereum_test_base_types/composite_types.py

Lines 487 to 492 in 56ea9f2

	class ForkBlobSchedule(CamelModel):
	"""Representation of the blob schedule of a given fork."""
	target_blobs_per_block: HexNumber = Field(..., alias="target")
	max_blobs_per_block: HexNumber = Field(..., alias="max")
	base_fee_update_fraction: HexNumber = Field(...)

We could even rename that type to BlobParams because the current name ForkBlobSchedule doesn't make much sense.

[marioevz]

This will break client tools that do not support this parameter yet.

The way we handle this is by implementing a ClassVar in TransitionTool that could default to False (example here:

execution-spec-tests/src/ethereum_clis/transition_tool.py

Line 75 in 56ea9f2

supports_xdist: ClassVar[bool] = True

), and then override it to True only for evmone.