Admin username mismatch between OKDP UI (adm) and Keycloak (admin) causes session conflicts

[jsanc525]

The OKDP UI admin user is configured as adm while the Keycloak admin user is configured as admin, creating issues logging into a service after logging into the other.

Steps to reproduce

1. Log in to OKDP UI as adm
2. Navigate to Keycloak UI
3. Observe login failure / wrong session

Keycloak UI when logged in as OKDP admin

OKDP UI when logged in as Keycloak admin

Expected: Both services share the same admin username for a more unified demo user experience.

Actual: OKDP uses adm, Keycloak uses admin, causing session/auth conflicts.

[abir-oumghar]

Hi, I opened #50 with a minimal fix: grant the master realm's native admin role to the adm user in default-context.yaml. That way a single account (adm/adm) covers both the OIDC-enabled services and the Keycloak admin console — no more session conflict.

Verified locally on the kind sandbox: logged into the Keycloak admin console and OKDP UI as adm/adm without any cross-service conflict. Existing role mappings on the admins group are untouched.