First pass at getting an approach for VMC development vs VMC release

- Use HEAD of our libraries (cfoundry, mothership, plugins, etc) in dev via Gemfile

- Use stable versions of our libraries in released gem via gemspec

Change-Id: I1ef2c1ec4d779844b005df0d4644d6159f02ac8d
Get the request and response traces into VMC crash file [finishes #41065481]

Change-Id: I8339e6912e7a0d3ea78cb0eddf3b54e63b58bc44
Merge "First pass at getting an approach for VMC development vs VMC release"
Add rake to the dev/test gemfile. Optimize the plugin.rb file to load the vmc specs only once.

Change-Id: I613ba74a6766773ae27cfe83221498786d683f19
Merge "Get the request and response traces into VMC crash file [finishes #41065481]"
Merge "Add rake to the dev/test gemfile. Optimize the plugin.rb file to load the vmc specs only once."
Include Gemfile.lock so that Travis can use that instead of building its own

Change-Id: Ib1afd8cbb4de2e137cb7591cce8ff66b1857296d
Fix specs to work with APIError signature change

Change-Id: Ifaeb00626ed84e8a1be816b5cab1a3021dc74938
bump to 0.5.0.beta.7

Change-Id: I7d846b2d6a3c901fd07d40cc3115b3641faec1ba