Remove the Gemfile.lock (closes #124)

According to [Yehuda](http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/), one should not commit the Gemfile.lock when a project is distributed as a gem.
Cleanup Travis yml
Lock to pessimistic versions in Gemfile and fix deprecations
Merge pull request #125 from opscode/sethvargo/remove_lockfile

[KNIFE-328] Remove the Gemfile.lock
initial commit
Merge pull request #132 from opscode/adamed-KNIFE-321

KNIFE-321: "knife-ec2" does not inform the user of the default us-east region
use chef search to figure out instance id from node name
Rename guess* methods to fetch to avoid implication of nondeterminism
Merge pull request #133 from opscode/adamed-KNIFE-253-delete-node-name

KNIFE-253: knife-ec2 should be able to delete instance based on chef node name
Add support for specifying an EC2 placement group when spinning up a new machine
Add tests and update Gemfile to include dependencies
Merge pull request #135 from opscode/adamed-KNIFE-160-placement-group-option

KNIFE-160: Add support for EC2 Placement Groups when creating new instances
Remove .rspec file so developers can manage their own
Test Ruby 2.0.0 and use progress formatter on Travis
Fix deprecations and run on Ruby 2.0.0
Use --format instead of --formatter
Fix README markdown and gemspec
Move development dependencies into gemspec
Use the correct branch on the badge
Merge pull request #143 from opscode/adamed-open-source

KNIFE-345: KNIFE-346: ReadMe and test deprecation cleanup contributions