OSGiBundleManager should get its address/port configuration from ServiceBindingManager

It includes a number of hard-coded ports, which won't be correct if a server is started with something other than ports-default:

<!-- Husky socket connector properties -->
<entry><key>org.jboss.osgi.husky.runtime.connector.host</key><value>${jboss.bind.address}</value></entry>
<entry><key>org.jboss.osgi.husky.runtime.connector.port</key><value>5401</value></entry>
<!-- HTTP Service Port -->
<entry><key>org.osgi.service.http.port</key><value>8090</value></entry>
<!-- Config Admin Service -->
<entry><key>felix.cm.dir</key><value>${jboss.server.data.dir}/osgi-configadmin</value></entry>
<!-- JMX bundle properties -->
<entry><key>org.jboss.osgi.jmx.host</key><value>${jboss.bind.address}</value></entry>
<entry><key>org.jboss.osgi.jmx.port</key><value>1098</value></entry>
<!-- JNDI bundle properties -->
<entry><key>org.jboss.osgi.jndi.host</key><value>${jboss.bind.address}</value></entry>
<entry><key>org.jboss.osgi.jndi.rmi.port</key><value>1098</value></entry>
<entry><key>org.jboss.osgi.jndi.port</key><value>1099</value></entry>

Documentation of SBM usage can be found at http://community.jboss.org/docs/DOC-9038. Unfortunately the conversion to Clearspace resulted in random parts of that doc disappearing. As an example, the deploy/naming-jboss-beans.xml file shows how the naming service itself is getting its ports from SBM; the same would be applied to the 1098/1099 entries above.