HTTP Verb based scopes incorrectly rendered multiple times from user perspective

JAX-RS apps deployed for OAuth2 by default use scopes that are based on the HTTP verbs supported by the app.

Because we render the translation of those scopes to non-technical end-users we have opted to generalize translations for groups of HTTP verbs based on simple "read" and "write" categorization. i.e. "GET", "OPTION", and "HEAD" all translate to "read data on your behalf".

This causes duplicate translations to be shown on the OAuth2 app > Scopes UI, whenever each verb based scope is rendered as a selectable scope (for example when there is no scope mapper).

Such duplicate rows should be combined, and assignable to the OAuth2 app as a unit.