Add Test to Catch Missing Permissions

[shamrickus]

This PR adds a test that checks that at least one user (admin) has all the permissions for the TO API routes. It will catch #6603 and #6609 with a test failure.

Note: until #6609 is fixed, the TO API tests on this PR will fail.

---

Which Traffic Control components are affected by this PR?

• Traffic Ops

What is the best way to verify this PR?

Run the TO API tests and verify they pass.

PR submission checklist

• This PR has tests
• This PR has documentation
• This PR has a CHANGELOG.md entry
• This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

[ocket8888]

The definition of the "admin" Role is that it has all Permissions past, present, and future. The set of Permissions afforded to the "admin" Role isn't even checked by Traffic Ops, so this is testing unintended behavior.

For example: The year is 2024, and I'm adding Foos as a new object to the Traffic Ops API. Foos are not related to any existing objects, and don't affect them in any way. Which users should be granted the FOO:READ and FOO:CREATE Permissions?

The intended answer is "none" and an "admin"-Role user will be responsible for doling out those new Permissions to whatever Roles need them. That's why we enforce an "admin" Role must exist, and why we treat it specially the way we do.