Remove unneeded dependencies espicaly on Jetty.

[smccauliff]

Remove some unneeded dependencies espicaly on Jetty. Jetty is only needed for
the JolokiaService, but it will start it's on embedded webserver should someone
want to run that service.
Narrow the scope of the testng dependency.

[smccauliff]

I tested that KM still works, locally but we don't have any testing for any of the metrics systems that people have contributed. Next time someone wants to modify that code they will need to provide some kind of test we can run to ensure we have not introduced regressions.

[gitlw]

LGTM

[andrewchoi5]

LGTM.

[sunnythepatel]

Hi @smccauliff ,
If jetty service has been removed how and what port I can check the UI on?

Thank you

[sean-rossignol]

@smccauliff @andrewchoi5 @gitlw just to confirm, seems like you removed the web gui shipped with kafka-monitor and instead are saying people can use the jolokia end points to look at the jmx metrics. Is that correct?
I'm porting our in house kafka-monitor/xinfra-monitor image to master 2.5.11 from 1.1.x and we used to stand up the xinfra-monitor web gui under a separate process. I want to confirm that this gui is no longer supported before I move remove our references to the old jetty webapp.