Better naming of queries and mutations to suit permission levels

[shreddedbacon]

As we're seeing more usage of this library amongst our own tooling, and that other people may be using this in their own tools too, we need to be more aware of when a particular function call may require elevated permissions than what general Lagoon RBAC would offer. For example, when a query or mutation requires platform-owner permission or greater, we should make this obvious some how in the query or mutation function name, or namespace them better within the client.

Also, recreating standard queries try to be as RBAC neutral where possible. This would allow for permission errors that would be returned to be genuine based on the requests that the user has performed knowingly. Some of this may not be possible with the current APIs structure, where some fields are retrievable by some roles, but we could still try to be as close to this as possible.