[ADVAPP-283]: Introduce Custom Reporting Capabilities

[danharrin]

Ticket(s) or GitHub Issue

• https://canyongbs.atlassian.net/browse/ADVAPP-283

Technical Description

Introduced reports, which are similar to caseloads in the way that table filters get stored in the database, alongside columns, and the table can be exported to CSV and Excel.

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Content or styling update (Changes which don't affect functionality)
• DevOps
• Documentation

Screenshots (if appropriate)

Screen.Recording.2024-01-30.at.18.57.13.1.mp4

Any deployment steps required?

A deployment step could be a command that needs to be executed or an ENV key that needs to be added, for example.

• Yes, please specify
• No

---

Before contributing and submitting this PR, make sure you have:

• Read the contributing guidelines.
• Title the PR with the ticket/issue number and a short description of the changes made. Or if no ticket/issue exists, title the PR with a short description of the changes made
• Linked a relevant ticket or issue or describe the issue/feature which this PR resolves/implements.
• Resolved all conflicts, if any.
• Rebased your branch PR on top of the latest upstream develop branch.

[Orrison]

Looks amazing! Just a few small nits.

[sonarqubecloud]

Quality Gate passed

The SonarCloud Quality Gate passed, but some issues were introduced.

1 New issue
0 Security Hotspots
No data about Coverage
11.7% Duplication on New Code

See analysis details on SonarCloud