When Camel creates a thread for processing using the provided ThreadPoolFactory we should customize the Thread name so diagnosing problems are easier.

JIRA related: https://issues.jboss.org/browse/SWITCHYARD-1979

Comment from kbabo:
To not mess with that, it would probably require a customization that wraps the thread factory that is passed in, delegates to newThread(), then calls t.setName(t.getName + "[custom name goes here]") on the returned thread