[TORQUE-910] Create Example Application Showcasing TorqueBox Features

Getting started guide extended with Poorsmatic application ste-by-step guide.
Importing source code of poorsmatic and the other two examples used in the getting started guide.
[TORQUE-740] Provide a mechanism to inspect torquebox configuration from code

Adds support for queues and topics:

TorqueBox::Messaging::Queue.lookup('/queues/something')
TorqueBox::Messaging::Queue.list

TorqueBox::Messaging::Topic.lookup('/topics/something')
TorqueBox::Messaging::Topic.list

Added documentation to the code and manual (with examples).
[TORQUE-987] Torquebox under Windows is case sensitive to the PATH environmental variable
Update to latest polyglot snapshot.

This will make jndi naming of destinations consistent with Immutant.
Use a durable topic for testing message scheduling.
Merge pull request #124 from goldmann/TORQUE-987

[TORQUE-987] Torquebox under Windows is case sensitive to the PATH environmental variable
Fix RubyRuntimeFactoryTest on Windows
Merge remote-tracking branch 'goldmann/TORQUE-740' into 2x-dev
List all queues and topics (TORQUE-740)

This is a slight modification of the pull request for TORQUE-740 to
list all deployed queues and topics instead of trying to limit the
list to those deployed inside the current application. The logic for
that is surprisingly hard (how do we handle destinations created at
runtime instead of in deployment descriptors?) and added extra
complexity that I'd like to keep out for the first iteration of this
feature.

If users ask for a way to limit the list to only those deployed from a
specific application, we can revisit this in the future.
Minor doc cleanup for TORQUE-740
Don't wrap publish_and_receive messages [TORQUE-1001]

This removes the wrapper, and sets the default ttl for the response
messages to 10 minutes.
Use the request message's encoding for the response message [TORQUE-1002]
Remove unneeded decode logic from publish_and_receive.
Don't log an error when we flip on XA for DB connections
Fix small file leak in basic_sinatra_spec integ
Fix MessageProcessors, XA, and priority (TORQUE-983)

We enlist the messaging session as an XAResource before HornetQ
acknowledges the message, thus preventing the issue where HornetQ
sends acknowledgement for messages with non-default priorities before
it calls onMessage.
Added a no-op Torquebox::Messaging::Message class
Added constructor to no-op Torquebox::Messaging::Queue
Added Torquebox.transaction
Pull the new no-op TorqueBox.transaction into its own file