Fix timing bug in Mongodb replicaset configuration

Since start_server() and restart_server() do not actually verify whether the
port is open and receiving connections (even though mongo starts up,
pre-alloc/other setup takes a few minutes), the replicaset recipe was failing to
establish a connection with the db.  The change to the initd file waits for the
port to be open before proceeding, ensuring that the replicaset recipe will
work.

Fixes #17
adding support for chef_gem wihch is available for newer versions of chef
sort config servers to mitigate MongoDB bug SERVER-5960
Replica set Reconfig action does not validate operation success
fix tabs
Fix mongos startup script, though only on RHEL family.
rhel init script should use pidfile for status and start
mongos does not support enable_rest.

Do not allow it to be applied, in case enable_rest is turned on for all
nodes or as a default attribute setting.
Add Recipe-Tester
Fix typo in README

'replicatset' shoud be 'replicaset'
Fix typo in replicaset.rb

'replicatset' shoud be 'replicaset'
Merge pull request #143 from amferraz/patch-1

Fix typos
Add new AMI
Try new ubuntu versions
Merge pull request #110 from emourant/chef_gem_support

Adding support for chef_gem wihch is available for newer versions of chef
follow up to #110 'just-in-case'
Version bump 0.13.2
Remove check if mongo gem needs to be added and just add it in the recipes

Running the gem install multiple times will not hurt anything.
Right now checking to see if the recipe is included is a bit backwards and causes issues if the cookbook is being wrapped.
Unless the cookbook is directly in the nodes run_list, it will not show up as included.
Remove check to see if the current recipe is loaded.

Yes, the current recipe is loaded, it's running the code.
whiitteeeeespppaaaccceeee