ARGO-5670 Fix Quarkus Authorization CDI integration after Quarkus Auth API changed

[cthermolia-grnet]

Update authorization service injection after Quarkus auth library changes

The authorization library was updated to support Mongo-based authorization queries. As part of this change, ResourceAuthorizationService is no longer intended to be injected and used directly.

The previous implementation injected the service through the interface:

@Inject
ResourceAuthorizationService resourceAuthorizationService;

This caused CDI resolution issues after upgrading the authorization dependency.

The authorization service injection has been updated to use the externally authorized implementation with the appropriate qualifier:

@Inject
@ExternalSystemAuthorization
OidcResourceAuthorizationService resourceAuthorizationService;
Changes included
Updated CDI injection to use OidcResourceAuthorizationService instead of ResourceAuthorizationService.
Added the @ExternalSystemAuthorization qualifier to correctly resolve the authorization bean.
Fixed CDI injection issues introduced by the authorization library update.
Restored authorization functionality with the new Quarkus authentication flow.
Impact

No API behavior changes are introduced. This change only updates the internal authorization service integration to be compatible with the latest authorization library version.

[kaggis]

⚠️ WAIT FOR SEPTEMBER for merging!: This is going to be merged in conjuction with ARGOeu/quarkus-auth#78 in beginning of September when everybody is back and can check the api with confidence