Have nightly tests against nightly generated artifacts

[GaAstDev]

Issue Addressed

Hello !
This PR aims to have a new nightly action that pulls the nightly generated artifacts from the CL specs repo and have the unstable branch run against them.

See: https://github.com/ethereum/consensus-specs/actions/workflows/nightly-tests.yml

Proposed Changes

To achieve this goal, this PR:

1. Creates a new workflow .github/workflows/nightly-tests.yml
2. Adds a new target in the Makefile run-ef-nightly-tests
3. Have the retrieval of the artifacts happen in testing/ef_tests/Makefile

Please note, this required a Github Authentication Token, I reused the one existing in the Github secret vault that has repo access: secrets.LIGHTHOUSE_GITHUB_TOKEN

[CLAassistant]

All committers have signed the CLA.

[michaelsproul]

Hi @GabrielAstieres, if you rebase on unstable that should fix all the CI failures (the target branch check won't update until you push a new commit, and the other two are fixed in unstable)

[GaAstDev]

Hi @GabrielAstieres, if you rebase on unstable that should fix all the CI failures (the target branch check won't update until you push a new commit, and the other two are fixed in unstable)

Hey @michaelsproul!
I've succesfully rebased on unstable. Thanks

[michaelsproul]

Thanks!

[GaAstDev]

Hey Michael @michaelsproul, did you get a chance to look at this? :)

[jtraglia]

It's up to the team, but personally I think we should remove this workflow.

[michaelsproul]

@jtraglia Are you concerned about noisy breakages, or accidentally revealing some bug on public CI? Both?

[jtraglia]

Just noise. Lots of the time, these tests will fail due to unimplemented spec changes. And I'm planning on aggregating the status of these in a new website (and eventually on Hive).

[michaelsproul]

Closing to prevent noisy breakages. LH generally won't be able to keep up with nightly test vectors

[jtraglia]

Hey @michaelsproul & @GabrielAstieres, sounds good. Let's open a new PR which just adds the ability to run the nightly reference tests, eg the Makefile stuff from here.

[michaelsproul]

Sounds good. Maybe even a Github action that we could trigger on demand?