feat: env vars to configure user error logging

[banders]

Description

Added a scheduled job to periodically delete old records from the 'user_error' database table. Added two new env vars to control the scheduled delete (DELETE_USER_ERRORS_CRON_CRONTIME and NUM_MONTHS_OF_USER_ERRORS_TO_KEEP), and also added one new env var to enable/disable user error logging altogether (IS_USER_ERROR_LOGGING_ENABLED).

Note: for local testing add the following to backend .env file:

IS_USER_ERROR_LOGGING_ENABLED=FALSE
DELETE_USER_ERRORS_CRON_CRONTIME="30 0 1 * *"
NUM_MONTHS_OF_USER_ERRORS_TO_KEEP=6

Fixes # GEO-700 and GEO-899

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

New unit tests. Updated existing unit tests.

Checklist

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• 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
• Any dependent changes have already been accepted and merged

---

Thanks for the PR!

Deployments, as required, will be available below:

• Frontend
• Admin Frontend
• Backend external API console

Please create PRs in draft mode. Mark as ready to enable:

• Analysis Workflow

After merge, new images are deployed in:

• Merge Workflow

[sonarcloud]

Quality Gate passed for 'Pay Transparency doc-gen-service'

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 SonarCloud

[sonarcloud]

Quality Gate passed for 'Pay Transparency Backend'

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud