Stub out marshalling of the private RSpec Time class copy

Recent versions of RSpec clone the Time class, to provide access to `now`
without having to worry about stubs left over from tests.  This led to a
failure in TorqueSpec when an attempt was made to marshall those objects.

This provides stubs that simply ship nothing -- no state -- for those
instances.  While this probably isn't optimal, it is sufficient to make remote
tests work as expected with RSpec 2.13

Signed-off-by: Daniel Pittman <daniel@rimspace.net>
Define `pending_fixed?` on exceptions shipped across the wire

TorqueSpec translates all exceptions thrown inside the container into
`Exception` instances, to avoid dependencies on classes that may not be
present on the client side.

Unfortunately, this has the side-effect of breaking detection of RSpec pending
tests that suddenly began to work -- a feature of newer versions.

This augments the marshalling to ship that extra field across the wire, and
attaches it appropriate exceptions; this gets RSpec 2.13 working again.

Signed-off-by: Daniel Pittman <daniel@rimspace.net>
Merge branch 'torquespec-6' of github.com:daniel-pittman/torquespec into daniel-pittman-torquespec-6
TorqueSpec can now execute multiple specs within a single deployment

The new configuration option called default_deploy specifies a filename where TorqueSpec should look for an optional default deployment descriptor. If the file exists then this default deployment descriptor is used for all specs except for those which explicitly define a deploy statement within their describe block. The default_deploy configuration option defaults to "default_deploy.yml" and TorqueSpec looks for this file in the spec_root directory.
Merge branch 'master' of github.com:gxbe/torquespec into gxbe-master