camel-resume-api: improve behavior with the master-component

The lifecycle of the resume strategy likely initializes too soon, which causes it to not respect the lifecycle of the master component. This causes it to load offsets too early and have outdated offsets if the primary node goes down and the secondary node goes up.

Possible solutions to investigate:

• initialize along w/ the component
• allow the components to reload the offsets on demand
• add a listener on the cluster view, so offsets can be reloaded transparently when the leadership is obtained