Address module export dependencies

[MartinWheelerMT]

What

• Switch from setup.py to pyproject.toml as this is now the preferred method in python.
• Update dependency versions in pyproject.toml to match those being used by the module.
• Rebuild mhs/common for the current changes.
• Rebuild dependent lock files.

Why

Setup.py files were specifying the local package dependencies as having different versions exported than than the pipfile. As, when this package is imported it uses these specified values, not the pipfile to determine dependencies. This should now be aligned. Modern python also uses pyproject.toml files instead of setup.py files so have migrated to this structure.

All dependent lock files we required to be regenerated.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Internal change (non-breaking change with no effect on the functionality affecting end users)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• I have performed a self-review of my code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have updated the Changelog with details of my change in the UNRELEASED section if this change will affect end users