Transfer groundControl from staff to admin route

[josh1248]

Description

Addresses #3031 by re-routing ground control from a staff to an admin route. P.S.: still figuring out the backend. Will further changes be required?

Type of change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [X] New feature (non-breaking change which adds functionality)
• [X] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [X] This change requires a documentation update
• [ ] Code quality improvements

How to test

• Enter the test environment as an admin, and see that you are able to enter ground control normally.

• Copy the ground control route (should be '/groundcontrol')

• Switch the test environment to be a staff

• Check that the ground control button is now missing.

• Paste the ground control route. A 404 route should be expected.

• Go to src/commons/navigationBar/AcademyNavigationBar and change the ground control route into a staff route.

• Log in as staff. Manually append '/groundcontrol' to the URL to get to the ground control screen.

• Attempt to delete an assessment, or mass publish an assessment through the ground control panel.

• A 403 Forbidden error should show up.

• Other functions, such as unpublishing or publishing of a single submission in the gradings table, should still be possible.

Checklist

• [X] I have tested this code - I have manually tested the website to check if I broke any frontend-backend links.
• [ ] I have updated the documentation

[coveralls]

Pull Request Test Coverage Report for Build 11008345446

Details

• 0 of 2 (0.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 31.449%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/pages/academy/academyRoutes.tsx	0	2	0.0%
<!--	Total:	0	2	0.0%	-->

Totals
Change from base Build 11007946528:	0.0%
Covered Lines:	4852
Relevant Lines:	14547

---

💛 - Coveralls

[RichDom2185]

Waiting for the BE PR before merging.

[josh1248]

@RichDom2185 backend PR is ready now. I have replaced all non-dangerous routes to use a "/staff" instead of "/admin" URL to connect to the backend. I have also changed the routes in the backend directly. All seems good, but I am not sure if I have advertently broken some frontend-backend link. Any automated way to test it?

[RichDom2185]

Any automated way to test it?

@josh1248 not really, I think best to just not touch it. Refer to my comments above.

Basically your endpoints paths should be related to your resource.

E.g. GET /users/{id}/name

or something like that