[breaking change] Stop creating a mongodb_instance in mongodb::default

[josephholsten]

From edelight/chef-mongodb#179

the logic of https://github.com/edelight/chef-mongodb/blob/master/recipes/default.rb#L42 is absolutely maddening in it's odd dependence on knowing exactly what recipes are in the run list. In particular, it doesn't play nice with wrapper cookbooks which may set up replicasets via include_recipe, not through node or role run lists. Don't get me started on mongos's search.

I propose:

• renaming helper recipes to begin with an underscore, including: install -> _install_package, 10gen_repo -> _mongodb_repo,
• keep 'standard' usage recipes top level: configserver, mongos, replicaset, shard, and move the default instance into its own mongod recipe
• also move mongo_gem -> ruby to match opscode's mysql, xml, &c cookbooks
• have default not do anything!

[shortdudey123]

@josephholsten counter point: i want to setup a single mongo instance without much config
thoughts?

[josephholsten]

then I'd prefer the doc said something like:

## The simplest thing that could possibly work

To spin up a minimal mongodb service with reasonable defaults, add `recipe[mongodb::mongod]` to your run list.

[shortdudey123]

That works, going to move this to v2 to avoid making v1 too complicated

[github-actions]

Marking stale due to inactivity. Remove stale label or comment or this will be closed in 7 days. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help! Thanks, Sous-Chefs.