Regression: PulsarAuthorizationProvider initialization

[EronWright]

Describe the bug
Existing implementations of AuthorizationProvider that extend PulsarAuthorizationProvider may regress following PR #12064. The initialization method is not called.

The reason seems to be that PulsarAuthorizationProvider::initialize(ServiceConfiguration, PulsarResources) does not call PulsarAuthorizationProvider::initialize(ServiceConfiguration, ConfigurationCacheService). In other words, the PulsarAuthorizationProvider defeats the back-compat logic in AuthorizationProvider.

To Reproduce
Steps to reproduce the behavior: use MultiRolesTokenAuthorizationProvider or AuthorizationProviderOAuth. Observe that the provider is not initialized.

Expected behavior
Initialization of authorization provider.

[EronWright]

@merlimat please take a look.