Don't reactivate authenticator on configuration change

Due to some refactorings of auth core, the Sling Authenticator is currently re-registered if its configuration changes. This has unwanted rippling effects on all components depending on the authentication support service.
Configuration changes should be handled via modified events internally