Some tidying around step exporters
Improve step export for jmx handler
Commit work in progress on step invokers
Fixes to JMX remoting for 2.x
Check parameter types when exporting step invokers over jmx.
Don't send ChorusContext type over the wire, send a generic Map instead so we're free to change ChorusContext implementation
Type coercion is now the responsibility of StepInvoker and so takes place remotely for remote step invocations
The step arguments corresponding to the groups in the step pattern are passed as List<String>
This means the interpreter doesn't have to have remote class definitions in its classpath, which it would need to preform local type coercion (e.g. for enum types) and will also play nicely with remoting to non-java components
Enable remoting without component suffix, allow handler classes to implement StepInvokerProvider to return step implementation directly
Use remotingPort in processes config properties rather than jmxport to support new remoting protocols