This JIRA has a dependency on adding OAuth scope support as well.
Was thinking that we should rename Client Templates to Client Scopes.
For oauth, oidc, and token exchange client asks for a specific scope
with the "scope" parameter. This "scope" parameter would be the name
of a client-id or a client scope (formerly client emplates. Clients
will be granted access to scopes in the admin console.
Our consent screen logic is a mess. We loop through every protocol
mapper and role stuffed in the token to blurt out a message on the
consent screen for each. Its messy, ugly, and not very easy to make
it look like you want. If we have Client Scopes, then clients can
consolidate mappers and roles into a single consent message that covers that group of mappers and role scopes.