Add module trying to discover all JMX ports available on target machine.

I have tested the new module (using auto and interactive modes) against a remote set of Tomcat instances hosted on a single machine (ubuntu) exposing each a JMX remote access:

![execexample01](https://cloud.githubusercontent.com/assets/1573775/2913841/4dd66cbc-d692-11e3-9521-7cf919e7dd83.png)

![execexample02](https://cloud.githubusercontent.com/assets/1573775/2913843/54926dbc-d692-11e3-8f89-62fa2be8c54e.png)

I have also added a check on superclass in main menu management because I have used a value object class in order to store port informations and the added check has to objective to only instanciate "Attack" sub class.

The strange thing pending is that a connection to a JMX mbeans server is always requested before to be able to run the new module. It's will be better if port discovering can be launch without requiring a "port" option and a JMX connection...

Let's discuss this point together :smiley: