III-6844 match apiKeys

[JonasVHG]

Added

• ClientIdResolver: Add interface to search for clients.
• KeycloakClientIdResolver: Add interface to search for clients on Keycloakd.
• matched-apikeys.feature: Acceptance tests.
• ApiKeysMatchedToClientIds & InMemoryApiKeysMatchedToClientIds: handle matching of apiKeys to clientIds.
• UnmatchedApiKey: Exception

Changed

• Authentication/AuthServiceProvider: register ApiKeysMatchedToClientIds.
• KeycloakServiceProvider: Register clientIdResolver.
• RequestAuthenticatorMiddleware: Add logging, inject ApiKeysMatchedToClientIds & ClientIdResolver, add logic to match apiKeys to clientIds.
• features/search/auth.feature: Update apiKey-name.

Related PF

• https://github.com/cultuurnet/appconfig/pull/1285

---

Ticket: https://jira.publiq.be/browse/III-6844

[JonasVHG]

@claude please review

[JonasVHG]

Claude suggested we should also add a CachedClientIdResolver, but I think it would be more prudent to wait till after the switch & we are sure we didn't forget lots of apiKeys.

[lucwollants]

I see a lot of new classes, but I don't see any unit tests? Although I see a new acceptance test, I think we still need unit tests for a sorter feedback loop.

[JonasVHG]

I see a lot of new classes, but I don't see any unit tests? Although I see a new acceptance test, I think we still need unit tests for a sorter feedback loop.

My mistake, I've added unit tests.