Add support for Cluster aware MessageSource

• User impact:

  High
• Similar Issues:

  None

Add a way to define MessageSources that, when running inside a cluster, ensures that only one instance is active at the time.
The message source must be active on the primary node only. In case the primary node goes down, the message source should be activated in the node that becomes the new primary node.