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
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.
deal with case where another server in the replcation set is already
initiated, and connect to it for config because we don't have a local
config yet. however, still support if our current server is already initialized
Merge pull request #43 from danieltahara/ISSUE-17-FIX

Fix timing bug in Mongodb replicaset configuration
Merge pull request #144 from cpuguy83/master

Remove recipe checks for gem install, move gem install to a separate recipe