chore(test-consume): resolve fixture release tag for consume cache

[spencer-tb]

🗒️ Description

Fix consume cache resolution for the fixture release scheme from ethereum#2888.

Release matching is now tag-namespace only (tests@vX.Y.Z, tests-<feature>@vX.Y.Z), so pre-tests-tag releases (stable/develop) no longer resolve, and @latest resolves the highest version rather than the most recently published.

Usage

All release inputs below work with consume cache (and any consume subcommand's --input):

# mainnet (tests) releases
uv run consume cache --input=latest
uv run consume cache --input=v20.0.0
uv run consume cache --input=tests@latest
uv run consume cache --input=tests@v20.0.0

# feature releases, with or without the tests- tag prefix
uv run consume cache --input=bal@v7.3.2
uv run consume cache --input=tests-bal@v7.3.2
uv run consume cache --input=glamsterdam-devnet@latest
uv run consume cache --input=benchmark@latest
uv run consume cache --input=zkevm@latest

🔗 Related Issues or PRs

Follow up to ethereum#2888

✅ Checklist

• All: Ran fast static checks to avoid unnecessary CI fails, see also Code Standards and Verifying Changes:

  just static

• All: PR title have the form <type>(<area>):, where <type> and <area> come from an approrpriate C-<type>, respectively A-<area>, label. The title should match the a target squash commit message.
• All: Considered updating the online docs in the ./docs/ directory.
• All: Set appropriate labels for the changes (only maintainers can apply labels).

Cute Animal Picture