CI/CD Test Harness Update

[jasercion]

The CI/CD system overhaul needs to be better integrate with the tests. Test results should display cleanly in the pipeline dashboard, be easily accessible, and should ideally be able to be used as process triggers or blockers. It would also be useful for run results to be available via reports sent by email or, even better, Slack. This will need to be done in conjunction with Fermitools-conda fermi-lat/ScienceTools#71.

[JamesAmrhein]

The CI/CD system overhaul needs to be better integrate with the tests.

• Test results should display cleanly in the pipeline dashboard, be easily accessible, and should ideally be able to be used as process triggers or blockers.
  Status: Test results have been integrated into the main dashboard.
  Here's an example image:

TODO: Further discussion is needed for these two items: process triggers or blockers.
Our first priority was to get a full E2E CI/CD running with Github Actions. That is currently running on the MASTER branch.
We even have a "weekly build" scheduled/ran every Monday morning as a sanity check.

• It would also be useful for run results to be available via reports sent by email or, even better, Slack.
  Status:
• Email : Every time a GHA run is completed, we get an email like this:

* Slack : The fermitools-pipeline channel gets a message after each run, like this:

It's wordy, and longer than I originally intended, but it's content contains everything we wanted it to have.

• This will need to be done in conjunction with Test Script Improvements #71.
  TODO: Will update that ticket with developer/rabbit hole details.