[ADVAPP-23]: Implement authorization methodology for querying particular fields

[danharrin]

Ticket(s) or GitHub Issue

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

Technical Description

You are now no longer able to see user relationships unless you have the view permission for that user.

You are now no longer able to view email addresses in responses (inc nested relation responses) unless you have the user.view-email permission.

You are now no longer able to query email addresses in requests (inc nested relation queries) unless you have the user.view-email permission.

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)

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 main branch.

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues

Measures
0 Security Hotspots
No data about Coverage
0.4% Duplication on New Code

See analysis details on SonarCloud