feat: WIP reinvigoration of package management tooling

[butler54]

Types of changes

• Hot fix (emergency fix and release)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation (change which affects the documentation site)
• Breaking change (fix or feature that would cause existing functionality to change)
• Release (develop -> main)

Quality assurance (all should be covered).

• My code follows the code style of this project.
• Documentation for my change is up to date?
• My PR meets testing requirements.
• All new and existing tests passed.
• All commits are signed-off.

Summary

This is a reinvigoration of the package management for compliance trestle to be the latest possible.

It also eliminates some dependencies which don't have support.

Closes:

Closes: #1728

Key links:

• Sonar coverage

Before you merge

• Ensure it is a 'squash commit' if not a release.
• Ensure CI is currently passing
• Check sonar. If you are working for a fork a maintainer will reach out, if required.

[butler54]

Putting here for some visibility. Not quite ready for review yet.

[butler54]

@jpower432 - any thoughts on hatch vs flit / poetry? I'm going to hold off until we have a clear path forward.

[jpower432]

@butler54 I have used poetry in other projects, but since the design includes dependency locking, I think it might not be best for our use case given #1715. hatch seems like is would be easier to use across the different project types that we have.