QA Test - Clean exit

[mriccobene]

This is a first "smoke test", part of the QA practices to help devs and the support team to identify as soon as possible, code regressions that are not detected by the actual Erigon CI/CD test suite or are not easily detectable with a standard Github Action workflow because they need a long running execution of Erigon.

This QA test runs on a self-hosted github action runner that is hosted on our bare metal machine.

It launches Erigon in detached mode and simultaneously a python script implementing the test logic. In this case, the script after a certain amount of time sends a signal corresponding to ctrl-c and looks in the logs to verify that Erigon has exited cleanly.

The python script is part of our private erigon-qa repository and it is available on our machine.

Despite this, the QA tests will be seamlessly integrated into our github space and will be visible next to the other tests performed in the usual way.

Quality assurance has a wide scope, it is a big topic. We will start with a first, more focused goal: building a smoke test suite. Next, in the long run, we will build the service that takes the execution metrics.