Attempt to run trunk & check for FIXMEs on PR

[katybaulch]

Description

Enable trunk check for admin backend repo. More info on trunk check here.

• Migrated from using python based git pre-commits to using trunk to speed and standardise across all repos
• Moved Python precommit validation CI job into reusable workflow that can be used in other Python repos
• Fixed all auto-fixable problems using trunk
• Enable trunk check and fmt actions as precommits (only for changed files)
• Explictly add app, integration_tests and unit_tests folders to project packages so Pyright doesn't give missing import errors
• Install using no-root in dockerfile to prevent install error
• Migrated all makefile commands to use Docker Compose v2
• Enable the following tools for this repo by default (trunk will automatically recommend ones to remove or add as your project changes):

• actionlint
• bandit (on non test files)
• black
• checkov
• git-diff-check
• hadolint
• isort
• markdownlint
• osv-scanner
• the precommit hooks detect-aws-credentials, check_json and end-of-file-fixer . A more exhaustive list can be found here, but they need to be manually enabled in the trunk.yaml file
• prettier
• pyright
• ruff
• shellcheck
• shfmt
• taplo
• terrascan
• trivy
• trufflehof
• yamllint

Proposed version

Please select the option below that is most relevant from the list below. This
will be used to generate the next tag version name during auto-tagging.

• Patch
• Minor version
• Major version

Visit the Semver website to understand the
difference between MAJOR, MINOR, and PATCH versions.

Notes:

• If none of these options are selected, auto-tagging will fail
• Where multiple options are selected, the most senior option ticked will be
  used -- e.g. Major > Minor > Patch
• If you are selecting the version in the list above using the textbox, make
  sure your selected option is marked [x] with no spaces in between the
  brackets and the x

Type of change

Please select the option(s) below that are most relevant:

• Bug fix
• New feature
• Breaking change

How Has This Been Tested?

Please describe the tests that you added to verify your changes.

Reviewer Checklist

• The PR represents a single feature (small drive-by fixes are also ok)
• The PR includes tests that are sufficient for the level of risk
• The code is sufficiently commented, particularly in hard-to-understand areas
• Any required documentation updates have been made
• Any TODOs added are captured in future tickets
• No FIXMEs remain

[linear]

PDCT-916 Add precommit hooks to db-client to bring in line with other repos