chore: archive ethereum/execution-spec-tests post-weld

[danceratopz]

In ethereum/execution-specs and ethereum/steel-website:

• Stop publishing test fixture releases on ethereum/execution-spec-tests:
  • feat(ci): overhaul fixture releases #2888
• Ensure consume cache works.
• Improve new steel.ethereum.foundation doc URLs for docs that come from the default dev branch.
  • feat(ci): deploy default branch docs at /docs/execution-specs/ #2973
  • feat: deploy default branch docs at /docs/execution-specs/ steel-website#59

In ethereum/execution-spec-tests:

• Update README:
  • remove most content; add simple archive notice
  • add links to The Weld blog announcement and execution-specs, also for releases.
• Final deployment to eest.ethereum.org with archive notice and redirects.
  • Add redirect from eest.ethereum.org to steel.ethereum.foundation/docs/ #2685
  • Examples:
    • https://eest.ethereum.org/ -> landing page with explainer
    • https://eest.ethereum.org/main/tests/cancun -> https://steel.ethereum.foundation/docs/execution-specs/tests/cancun/
    • https://eest.ethereum.org/main/foo?ref=eest.ethereum.org -> execution-specs 404
• Disable docs deploy within eest to avoid getting redirect page clobbered.
  • chore(ci,docs): archive eest.ethereum.org and stop docs redeploys execution-spec-tests#2323

In ethereum/EIPs

• Update EIP-1: Remove execution-spec-tests from allowed link exceptions EIPs#11845 @danceratopz
  • Update EIP-1.md to remove any mentions of execution-spec-tests.
  • Update all links to execution-spec-tests in any EIPs to point to the new test location in execution-specs.

[marioevz]

Modify README.md to point newcomers to EELS.

[marioevz]

We might need to keep main branch frozen for a while until we know that most teams that could be using the code (as opposed to the releases of the fixtures) have properly migrated over to EELS.

This will require probably hand-holding and reaching out via Eth R&D to see who could need help with this.

TL;DR:

• main stays as is, frozen with the exception of README.md updates that help teams transition to EELS.
• In parallel we can create forks/osaka, forks/amsterdam branches that contain the filled fixtures from EELS.

[github-actions]

This issue has had no activity for 60 days and has been marked as stale.