Introduce a way to update broker service configuration dynamically about pulsar

[rdhabalia]

• Mark dynamic settings with an annotation in ServiceConfiguration : [Yes, Included in commit]
• Have a way to register for config changes events (this may be useful for certain class of variables) [Yes, Included in commit]
• Otherwise, just read the "dirty" value from the ServiceConfiguration instance (don't store it in local variable and don't use any mutex [Have done similar change]
• Add a REST handle to change key/value pairs, that only accept variables marked as dynamic [Yes, Included in commit]
• Store all dynamically configured variables in a single z-node in "properties" format [Yes, Included in commit]
• At startup log the content of that z-node and log each time a change is detected [Yes, Will do]

This commit includes almost all above suggestions. Once you review and if you think it is fine then I will go ahead and complete full changes.

[merlimat]

Few random ideas (haven't looked at the code yet):

• Mark dynamic settings with an annotation in ServiceConfiguration
• Have a way to register for config changes events (this may be useful for certain class of variables)
• Otherwise, just read the "dirty" value from the ServiceConfiguration instance (don't store it in local variable and don't use any mutex
• Add a REST handle to change key/value pairs, that only accept variables marked as dynamic
• Store all dynamically configured variables in a single z-node in "properties" format
• At startup log the content of that z-node and log each time a change is detected