Unify way to address configuration on backend

[blcham]

As a developer, I would like to see configuration in application.properties unified, I see the following:

security:
  provider: internal

appContext: http://localhost:5173
oidc.RoleClaim: realm_access.roles
cors.allowedOrigins: "http://localhost:5173,http://localhost:4173"

spring.security.rolePrefix: ff-

From this fast look, I would unify it in the following way:

security:
  provider: internal
  cors.allowedOrigins: "http://localhost:5173,http://localhost:4173"  
  oidc.RoleClaim: realm_access.roles
  rolePrefix: ff-

appContext: http://localhost:5173

In case rolePrefix is specific only for oidc, I would even move it to security.oidc.rolePrefix: ff-.

A/C:

• unify the naming convention in application.properties file
• modify configuration in deploy/keycloak-auth and deploy/internal-auth folder
• modify configuration in 23ava-distribution

[kostobog]

@blcham
Is this unification also applied to record-manager and analytics backends?
I am asking because I think I have to change this part in distribution docker-compose:

x-access-for-local-development: &local-dev-env
  cors.allowedOrigins: "http://localhost:4173,http://localhost:5173"

to this:

x-access-for-local-development: &local-dev-env
  security.cors.allowedOrigins: "http://localhost:4173,http://localhost:5173"

[blcham]

yes we should refactor everywhere.

[kostobog]

@blcham
Ready to review.
See PRs #167, kbss-cvut/fta-fmea-ui#654 and kbss-cvut/23ava-distribution#153

[blcham]

Adding PRs kbss-cvut/record-manager#81, kbss-cvut/record-manager-ui#237