Configure bind and cluster over the specified addr

This patch allows for binding rabbit and epmd to the specified
address.  Useful when wanting to cluster over a different interface.
In our case we want clustering to occur over our reliable 20Gb network,
vs our management network.

There are a couple prerequisites to this configuration:
  * The address provided to `rabbitmq['erl_networking_bind_address']`,
    requires f/rDNS.
  * The hosts provided to `rabbitmq['cluster_disk_nodes']`, must resolve
    to IPs on the same network as `rabbitmq['erl_networking_bind_address']`.

Sample configuration, wanting to cluster over eth1.
  host1:
    - eth0 - 192.168.0.10 (host1)
    - eth1 - 172.16.0.10 (host1-ops)
  host2:
    - eth0 - 192.168.0.11 (host2)
    - eth1 - 172.16.0.11 (host2-ops)

Configure your wrapper cookbook such that:

  `node.override['rabbitmq']['erl_networking_bind_address']` = #{eth1_address}
  `node.override['rabbitmq']['nodename']` = "rabbit@host1-ops" or "rabbit@host2-ops"
  `node.override['rabbitmq']['erl_networking_bind_address']` = ["rabbit@host1-ops", "rabbit@host2-ops"]

Change-Id: Ib815e8fdf50dad7ea47e2484e93599fa631b4e6f
renamed all_management to lwrps
fixed test matrix and added erlang-esl testing