Add documentation how to configure and control Camel JMX naming

See ENH-31

I have implemented this solution and backported it to the Fuse Camel 2.9 branch as well.

This page has more details (when the static html is updated at Apache)
http://camel.apache.org/camel-jmx.html

Basically now you can easily control the JMX names to make sure they never change. For example this is best practice with Fuse ESB as the JMX names will by default use the bundle id as prefix. And the bundle id, can change over time. Such as if you uninstall/install your application. Or potentials if you upgrade / reset the ESB etc.

This causes problems for FuseHQ as it cannot understand if the JMX names have changed. And thus our FuseHQ customers see old applications which become stale. And over time this clutter etc.

So now you can explicit set the JMX and Camel names independently. But often you want this to be the same, so if you want a fixed name then just do in the XML file

<camelContext id="myApp" managementNamePattern="#name#" ...>
   ...
</camelContext>

In the <camelContext> we must set both the id and managementNamePattern to make it fixed and never change.
The id is the CamelContext name, and we most often want this as part of the JMX names as well, and hence we use #name# in the managementNamePattern, which simple refers to the CamelContext id.

The managementNamePattern supports a number of patterns which are listed on the wiki page (link above). For example there is a #bundleId# and so forth.