chore(fill,ci): only generate each fixture once per release

[danceratopz]

For "full" (aka "stable" releases), we provide two tarballs for client teams:

• fixtures_develop.tar.gz: All tests up to and including the current fork under active development.
• fixtures_stable.tar.gz: All tests up to and including the current fork deployed to mainnet.

Two tarballs are currently provided as a convenience to client teams.

The fixtures_develop tarball is a superset of fixtures_stable: It contains all the tests from fixtures_stable, but additionally:

• All tests filled with the current development fork.
• Tests specific for the current development fork.

Currently, tarballs are generated directly by fill in two separate commands:

execution-spec-tests/.github/configs/feature.yaml

Lines 2 to 8 in 5220d21

	stable:
	evm-type: stable
	fill-params: --until=Prague --fill-static-tests --ignore=tests/static/state_tests/stQuadraticComplexityTest
	develop:
	evm-type: develop
	fill-params: --until=Osaka --fill-static-tests --ignore=tests/static/state_tests/stQuadraticComplexityTest

which means that each test fixture is generated twice.

I would suggest we generate --until=Osaka by default and write a filter_fixtures cli utility:

filter_fixtures --input=fixtures_develop/ --output=fixtures_stable/ --filter=name,regex

where name,regex could be fork,Osaka, for example, and we define filters within the cli utility that map to fixture field names (state and blockchain fixtures aren't consistent). This would allow us to copy all the fixtures across but remove the dev fork fixtures.

[felix314159]

I agree that we should avoid double filling.

But seeing how many changes #2045 introduces I wonder whether there is a simpler solution. Why does fixtures_develop.tar.gz have to include anything that is not a development fork? If stable only contains stable, then why should develop include sth that is not develop?

If the develop tar gz only contains the current dev fork and nothing else we only have to change one line of code. We can then also tell the client teams that stable and develop have no intersection (which from the resulting file sizes should be obvious anyway)

[felix314159]

And if the concern is 'but what if client teams forget to download one of the two tar.gz files' then we can just decide to only offer fixtures.tar.gz, which contains 'fixtures_develop.tar.gz' and 'fixtures_stable.tar.gz'