Dynamic scopes for OIDC

[WilliamSoderberg]

Description

Implementation of dynamically loaded scopes in the OIDC connection process. Enabling custom scopes to be used as username.

Closes #1363

According to the contributing guide, A PR should contain:

• A clear description of why it was opened.
• A short title that best describes the change.
• Must pass unit and integration tests, which can be run checked locally prior to opening a PR.
• Any additional details for functionality not covered by tests.

Additional Details
Except for the already provide oidc_test, test were made using non exsistent scopes to test for failure.

When invalid userIdentifier is used:

{"status":500,"message":"no valid username found for identifier 'test'"}

[gtsteffaniak]

thanks for the work to contribute this feature. I do plan to merge this, but it will go on the beta track. I am not making any disruptive changes until I have a stable release track ready.

Then this will merge to beta so it won't affect stable.