Core, REST: properly close resources when catalog initialization fails

[adutra]

If initialization fails, for example when fetching the config, the AuthManager won't be properly closed and will leak resources.

Same for the catalog's RESTClient or AuthSession, if some error is thrown before they are added to the CloseableGroup.

[nastra]

changes LGTM but wouldn't we have a similar issue in other places where the auth manager is used, such as VendedAdlsCredentialsProvider/ OAuth2RefreshCredentialsHandler? I think in those two classes the CloseableGroup should be instantiated much earlier and managed outside of the close() method

[adutra]

changes LGTM but wouldn't we have a similar issue in other places where the auth manager is used, such as VendedAdlsCredentialsProvider/ OAuth2RefreshCredentialsHandler? I think in those two classes the CloseableGroup should be instantiated much earlier and managed outside of the close() method

@nastra I think they are fine? As it stands now, in these classes, every closeable field that is written will get closed when the close() method is called. The CloseableGroup is just a trick to avoid a bunch of nested try-finally blocks.

[adutra]

Also: CloseableGroup is not serializable, so that would be a problem for VendedAdlsCredentialProvider.