Expected Behavior

• Separating out the integration tests related to rbac and remote functionality.
• We have to spin up the only one instance of the keycloak for all the integration tests.

Current Behavior

All the local integrations are running in the same job so if we can separate the tests related to rbac and remote functionality it provides more flexibility.

Currently the keycloak instance is spinning up multiple times even though we are using the dist groups. I have enabled the logs and can see multiple keycloak instances being spinning up. This is causing memory issues and eventual failure of the integration job on the PR. We have to spin up the only one instance of the keycloak.

Steps to reproduce

Enable the logger info by passing extra arg -s to pytest command in make file. You can see the logs Starting keycloak instance being printed multiple times.