Validate if we can use the 'auto restart on rotated credentials' and 'auto invalidate cache' together

[stijnmoreels]

Describe the bug
Because the 'auto invalidate cache' works with every secret, it will also work with the secret that is defined in the 'auto restart on rotated credentials'. Because of this, when the invalidate job is registered before the auto rotate job, it will 'steal' the Azure Key vault event.

The problem in this case, is that we want both message handlers to handle the Azure Key vault event.

To Reproduce
Steps to reproduce the behavior:
Register both 'auto invalidate cache' job and 'auto restart on rotated credentials' handler.

Expected behavior
Event gets handled twice.

Additional context
v0.4

We could investigate in adding a scope to the registered message handlers. In those cases, an incoming message will only be handled by the message handlers that were registered for a given job (message pump). This would allow us to handle the Azure Key vault event twice (in different pumps) and also handle it twice.

[stijnmoreels]

Related to arcus-azure/arcus.messaging#395