Add build-cookbook subcommand to chef generate and --delivery option to chef generate cookbook

[danielsdeleo]

• Add new option -d/--delivery to chef generate cookbook, which will create a .delivery/config.json and build cookbook in the generated cookbook.
• Add new generator subcommand, chef generate build-cookbook, which creates the .delivery content as above, but outside the context of generating a new cookbook. This includes the same auto-detection logic as pcb to determine if the project is a cookbook or not, and modify the generated content accordingly. Therefore, it can potentially replace the pcb cookbook's role in delivery init.

For both use cases, I compared the generated files to those created by delivery init -l, and confirmed there are no substantive differences.

[tyler-ball]

Is the name hard coding to keep it in line with existing behavior?

[tyler-ball]

I ask because we can specify the cookbook name in the .delivery/config.json so it doesn't need to be hardcoded. Not a huge deal either way

[danielsdeleo]

delivery init doesn't give you a choice in the matter, you always get build-cookbook. Even if you ask it not to make a build cookbook, the Delivery config.json it creates is still hard coded to a local build cookbook named build-cookbook. Given all that, it seems like demand for differently-named build cookbooks is low to nonexistent so I decided it's probably not worth the trouble to implement, but figured it's worth a note in the code to explain that I took a shortcut.