Manage tenant information into application - remove dependency on keycloak for rbac

[johnaohara]

The current tight coupling between Keycloak and RBAC for multi-tenancy is hindering adoption in different environments, specifically k8's.

If the tenant information is moved from keycloak into the application, and just use keycloak for IAM, the option to support public IAM providers and custom RBAC providers allows for greater integration with more environments

• Fallback to Basic authentication when keycloak URL is not defined #1146
• Provide Roles REST endpoint to retrieve user roles from the application #1187
• Migrate keycloak roles to horreum db tables #1188
• UI fetch keycloak roles through the backend #1255
• Add roles entity and roles table to the DB #1256
• Use roles table to perform row level security #1257
• Fecth roles from the DB into the SecurityIdentity object #1258
• Remove team cache  #1259
• New implementation of UserService #1260
• Migration strategy for roles #1261

[johnaohara]

removing from 0.12 milestone, most tasks have been completed, the outstanding issues (#1257) etc will not be completed in for 0.12