Auth: Decouple client and hook registration

[kalleep]

What is this feature?
Currently all client and hook registrations happens in the service provider factory. This prevent us from injecting this authn into other services that needs it due to circular injections. We decided early on to move the registrations into their respected service but never got around to it.

As a first step I created a new component that depends on authn.Service and all other services. The only think this component does is register clients and hooks and then return an empty struct. I then use the backgroudservice injection hack to make sure this is run on startup.

Which issue(s) does this PR fix?:

Fixes #

Special notes for your reviewer:

Please check that:

• It works as expected from a user's perspective.
• If this is a pre-GA feature, it is behind a feature toggle.
• The docs are updated, and if this is a notable improvement, it's added to our What's New doc.

[IevaVasiljeva]

LGTM with a small comment about fixing logging.

[Jguer]

if we can hold just a bit to merge OBO, it would save me a lengthy rebase

[kalleep]

if we can hold just a bit to merge OBO, it would save me a lengthy rebase

That is why I have not merged this one yet. I already have caused some conflicts for you 🙈

[alexanderzobnin]

We still have problems here I think. Authn service depends on usagestats.Service and login.AuthInfoService and they are depend on accesscontrol service. Which makes it impossible to inject authn service into access control one.

[kalleep]

@alexanderzobnin I managed to get rid of usage stats as a dependency but the other problem is AuthInfoService depends on SecretService that depends on UsageStats. Maybe the proper fix if to remove accesscontrol.Service as a dependecy in usage stats. The only think it does is register a fixed role and we can probably just move that declaration and registration into access control package instead, WDYT?