Mule integration test does not work with all rules enabled

[safris]

The integration test needs to work with these properties removed.

[jam01]

So the issue is between regular grizzly-http-server and mule-4-http-server rules. The grizzly setup that the http-service uses is not supported out of the box by the regular grizzly rule so that one has to be disabled. All other plugins are disabled because they slow down the tests significantly.

Also there are some rules that should probably always be disabled with Mule 4 such as java-concurrent and maybe others. They generate spans through the regular lifecycle of the runtime and are unrelated to the actual services, though you may still want to have them enabled for integration testing purposes.

[safris]

We need to figure out an automatic rule exclusion mechanism -- one that will operate by detecting whether the runtime has Mule or Grizzly, and adjust the instrumentation appropriately. We do this for Lettuce 5.1 and Lettuce 5.2.