Integration tests setup fixes (Git, CoilMQ)

Git setup wasn't working as expected, leaving the respository in
detached HEAD status. Using git.cmd.Git instead of the repository
object works fine. CoilMQ is not closing listening socket on shutdown,
so if we try to use the same socket again, it won't work. Just closing
the socket manually to fix the issues.
Integration testcases for MCollective 2.0.x/2.2.x
More CoilMQ integration tests work

Running CoilMQ from the tests won't work, CI will need a new approach.
Added travis-cookbooks as Git submodule
Updated Ruby version and renamed Ruby gemset
Added Vagrantfile for RabbitMQ server node
Custom config file per test package
Messages don't hardcode collective

Just for compability adding a default collective 'mcollective'.
Using Stomp connector for integration tests

Adding some connector checks/fixes (to be replaced by different classes
implementing connector details).
Adding some asserts on MCollective agent requests
Adding script for starting MCollective

Right now tests require starting MCollective manually, so adding an
script for that.
Adding script for running mco commands
Removing CoilMQ integration
Addding verbose option to py.test args
Sending command line arguments to mcollectived
Running MCollective automaticaly again (as daemon)
Waiting 2 seconds for MCollective

Or tests will finish before MCollectives get connected to RabbitMQ. This
should be done in a smarter way, but not really sure how.
Merge branch 'feature/vagrant-rabbitmq-integration' into feature/mcollective_integration_tests