[TORQUE-795] Allow changing processors' concurrency setting without restarting torquebox or redeployment of an app
Merge pull request #4 from goldmann/TORQUE-795

[TORQUE-795] Allow changing processors' concurrency setting without restarting torquebox or redeployment of an app
Add getMessageProcessorClass() to allow retrieve the class name of the message processor implementation
Be more verbose in the trace log
Allow to set the MessageProcessorGroup concurrency to 0
Allow portions of the startConsumer process to be overridden.
Add and expose the 'synchronous' parameter used to determine if the message processor should reply
Changes to support something close to AS 7.2.
Use the quartz 2.x builder API.
Add support for at-style jobs.

This also includes a class rename (BaseJob -> NotifiableJob) that will
break TorqueBox until the same change is made there.
Move polyglot-core and polyglot-web to be first-class JBoss modules.
Mix in more dependencies.
Move AtRuntimeInstaller to the core module.

And get rid of core-extensions, since it's no longer needed.
Only install the services if we haven't already.

TorqueBox and Immutant both use this processor, and both key off of
the presence of ApplicationMetaData. Now that -core is a module, the
ApplicationMetaData class is only loaded once, so the processor can
fire twice in an overlay type siuation.
Cache and HASingleton modules don't need to bring their own Core jars.
Even less jar duplication.
Rebase AS.
Remove SNAPSHOT
Rev stilts.
Make the underlying web session accessible.