QBFT soak test run nightly, with status badge

[jflo]

There is a long-running integration test covering QBFT networks, implemented via the acceptanceTestBftSoak target in gradle.

This is a useful, but long (2hrs?) test, and so running it nightly should be sufficient to alert us to any introduced regressions.

[jflo]

• what should be the consequences of job failure?
• how do we expect to track success/failure?
• failure should be a blocker to release

[matthew1001]

Thanks for looking into this @jflo Some thoughts on the above.

• Test failure
  • Maybe to start with we could look at raising an alert in the besu-github discord channel to indicate the failure. I don't mind being tagged in the alert at least to begin with
  • Can other GHA's be dependent on the most recent scheduled run being green? I'm thinking of release-related GHAs particularly.
• Tracking & release
  • Perhaps part of the release process is to manually check the recent scheduled runs to ensure that the most recent one is green
  • If they have clearly gone pass, pass, pass, fail, fail, fail... then whoever is doing the release process might need to investigate more closely
  • If they are intermittent then maybe it's a sign that the test's reliability needs looking into