Refactor API keys "super user" to "full access"

What does this MR do and why?

• Refactor API key "super user" to "full access" as it does not give super user rights, but rather allows full access to all elements that the user already has access to.
• Technically we could have just changed the label on the page, but I think a refactor was necessary to make the codebase a bit more readable and clear.

#TODO

• Fix translations on the front end
• Disable input field for API key creation that users don't actually have access to. (This is not a security issue. We won't allow users to add permissions they don't have, but it's not clear on the front end that this isn't allowed.)

Screenshots or screen recordings

___These are strongly recommended to assist reviewers and reduce the time to merge your change.___

Please include any relevant screenshots or screen recordings that will assist
*reviewers and future readers. If you need help visually verifying the change,*
*please leave a comment and ping a GitLab reviewer, maintainer, or MR coach.*

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• Have you checked this doesn't interfere/conflict/duplicate someone elses work?
• Have you fully tested your changes?
• Have you resolved any lint issues?
• Have you assigned a reviewer?
• Have you applied correct labels?