Changed remote exception interface to transmit remote stack trace as a string (previous mechanism was failing to transmit any information about nested exceptions)
split process functionality out of the process handler and into a reusable process manager
split process functionality out of the process handler and into a reusable process manager
Added functionality to increment jmx and debug port for each process is created from a process config after the first within a scenario. The ports are reset when the scenario completes. Enhanced the remoting handler: when it fails to connect to a remote process using the location found in the remoting config, it will attempt to connect using configuration from the process manager.
Fix to remove extra info logging and correct ordering of increment jmx port and debug port
Revert the ChorusRemotingException changes and live with the known issues as discussed until we resolve in chorus 3.x
Initialize feature level resources on feature start for handlers scoped at feature level
Change scoping of initialize / load configs to feature initialization, to match past behaviour
update expected output for test
At present we can see errors relating to missing processes config when executing a remoting handler step - this can occur when we try to get a processes config to give us the jmx port to remote to, in the case this is a local process started by process manager. I changed this so if we can't discover a processes config to help us, we still log the issue as a remoting handler problem, otherwise the output is confusing
Merge branch 'emergeo'

Conflicts:
	chorus/src/main/java/org/chorusbdd/chorus/core/interpreter/HandlerManager.java
	chorus/src/main/java/org/chorusbdd/chorus/handlers/remoting/RemotingHandler.java