Enable drunc and small_footprint integration tests as CI workflows

[PawelPlesniak]

Description

Allows for the small footprint test to be ran as a CI workflow. This will be extended to the drunc integration tests, which focus on ensuring that the features that we rely on in all use cases (production, development, integ testing) remain functional.

Builds on

• Continuing Aurash's work on MSQT CI workflow #985
• enable and fix msqt in CI #928

Will be able to close #610, and any other subprocess integration test PRs and issues.

This has also refactored the structure of the CI workflows that the developer will need to consider into two workflows:

• Run checks at the development stage - runs standard checks including
  • linting
  • checking the __init__ file structure is correct
  • Checking links in docs
• Run tests - runs the unit (including publishing reports on the results and coverage), daqsystemtest integration tests, and the drunc integration tests

The Run tests workflow has been configured to run when a user takes a PR out of draft mode, which is the currently proposed development model.

The track_new_* workflows have also been extended to track in the drunc project board, and to assign the relevantt developers to the relevant PRs. An example of this working can be seen here

[PawelPlesniak]

I need to get tthe SSH daemon working, but the test now runs

[PawelPlesniak]

With commit a17ba8f, all the pods were able to be spawned, but they did not connectt witthin the timeout. I am running an 8 core test to see if this can fix the problem. The associated CI integtest run with k8s is here

[PawelPlesniak]

With the current commit, a kubernetes integration test ran successfully on CI
See this workflow for the output

[PawelPlesniak]

TODOs:

• Cache the generated nightly
• Remove the SSH setup for the k8s integtests, if possible
• Re-enable all the tests