Do not revert custom container name

[MarkBorcherding]

The readme states you can override the container name by doing something like:

  task :common do
    set :name, 'backend'
    # ...
  end

This doesn't seem to work. When you do that, you still get a container named the same as the project.

There are tests around it, but bin/centurion was messing it up, which is untested. I added some integration tests that actually spin up a Vagrant box and runs Centurion against it. I've excluded them from the the default rake and rspec runs. You can run them first running vagrant up and then running rake integration.

I'm not sold on keeping them, but this is something I've been using to troubleshoot this, and other problems I'm finding. It might be good to have working end to end examples.

At the very least, the fix to bin/centurion needs to be made.

[relistan]

Hi @MarkBorcherding you are right this it broken! I'd like to not introduce all this other stuff but bring in the fix. There's not a single commit I can cherry pick so I'm going to close this and merge make the fix myself. I agree we need end-to-end tests, but as is I don't see how to merge this.