An RFC to standarize on two workflows

This RFC proposes two workflows as "supported", and abstracts
as much of their differences as possible through the use of
additional generators and functionality in the 'chef' command.

If accepted, this RFC would also serve as a guide for tool makers,
as to what the requirements are for maximum converage in the Chef
community.

While other workflows are possible, this RFCs job is to say which
ones we support officially.
The problem to consider with Ruby is that's it's interpreted. It's the same problem as `metadata.rb` as `metadata.json`. Consider:

```ruby
name 'cookbook_foo'
version File.read(File.expand_path('../VERSION', __FILE__)).chomp
```

This will read a local file named `VERSION` to get the version. This will work, and when you upload to the server, you will get the **compiled** JSON version like this:

```javascript
{
  "name": "cookbook_foo",
  "version": "1.2.3"
}
```

Ruby gives us the ability to "depend" on external systems, which is both good and bad. I could see situations where using Ruby could actually cause us problems.

I'm :+1: on Ruby files, but this is something to consider.