feat: central package management

[MWClayson-NHS]

Description

These are changes to enable Central Package Management across the whole Cohort Manager Project.
Additionally to implement these changes we were required to create base images that have access to the following files

• Directory.Build.props
• Directory.Build.targets
• Directory.Packages.props

Base Image Process

• Created two new Docker build Files (Dockerfile.dotnet.base, Dockerfile.function.base) These will ensure the above files are copied over so the function is built correctly
• Created new CI/CD Step to build base images and push them to GHCR
• Updated all other docker images to use the base images.

CPM Changes

• Create root Directory.Packages.props file with versions of all nuget packages used across the whole product
• Removed Versions from all *.csproj files
• Created Directory.Build.props file to ensure the intermediary build step for functions does not error due to versions in the WorkerExtensions.csproj Files
• Created Directory.Build.Targets to prevent Worker Extension Files from being created when unit tests are being run / built

Context

This change solves two problems

• Package Drift, This change centralises the versioning of nuget Packages used across the project meaning that all packages will now be all aligned by version.
• Pre-building Shared Libraries should improve the performance of the ci/cd and local build process.

Type of changes

• Refactoring (non-breaking change)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would change existing functionality)
• Bug fix (non-breaking change which fixes an issue)

Checklist

• I am familiar with the contributing guidelines
• I have followed the code style of the project
• I have added tests to cover my changes
• I have updated the documentation accordingly
• This PR is a result of pair or mob programming

---

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

• I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

[github-actions]

Unit Test Results

✔️ Tests 975 / 975 - passed in 75.5s
📝 Coverage 47.76%
📏 4755 / 10228 lines covered 🌿 1167 / 2172 branches covered
🔍 click here for more details

✏️ updated for commit 6a01fe7

[MacMur85]

Can you please take a look at this archive branch and how we can target the GHCR using variables?
I think it would be slightly better in terms of the code.

dtos-cohort-manager/.github/workflows/stage-3-build-images.yaml

Line 199 in a74bfff

GH_IMAGE="${{ inputs.gh_registry }}/${{ github.repository_owner }}/${{ inputs.project_name }}-${{ matrix.function }}:latest"

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud