Clean up and abstract github pipelines

[butler54]

Issue description / feature objectives

The current setup of compliance trestle's github pipelines are robust, however, have been aging:

Brittleness and risk of errors

• Python versions are defined in multiple places
• Elements of the pipelines are (probably) necessarily replicated.
• Some areas particularly release management (see #1571) are tightly coupled making the pipeline brittle.

General updates

• The pipeline versions have not been updated recently (note the dependabot configuration should be updated to ensure that prompt alerts are configured)

Efficiency

• Caching is now inconsistently applied. This leads to long build times particularly for windows where the runners are slower.
• The pipelines are a bit bulky. There are two recommendations:
  • Currently three versions of python are testedL A lower bound, a mid version and an upper bound. Recommend that it's slimmed down to a minimum and maximum.
  • Remove or slim actions run on push to develop (which is unnecessary as the pipeline insists the code is up to date before merging so exactly the same)

Caveats / Assumptions

• Fundamental tech in the supply chain don't change

Completion Criteria

[butler54]

This would include #1559

[AleJo2995]

Hi @butler54 While issue triage today we were just wondering if this close is done or is there more pending work to do? I've seen the abstract python version in pipelines PR to be closed but not sure if that covers all the items in here. Assuming no, but just wanted to confirm. Thanks.