Add version, tags fields to script, tests

[bdarcus]

Partially addresses #17 and #25, this adds "VERSION" and "TAGS' fields to the
processor.py script, and to the former to all the tests.

It doesn't currently do much with the output, other than to add "version" and "tags" variables to the json test files, but the idea is we could do two things with this:

1. distinguish 1.0 and 1.1 tests (though we need to figure out how to address this suggestion on min and max version; maybe simply 1.0-1.1?)
2. tag tests that we think need documentation in the spec (which would be the next step); perhaps like docfix?

Below I note @fbennett agrees we could also use "description" field. I suggest people just start adding that when they see a need for it on a test. The script will simply ignore it currently.

My suggestion on 2, then: on those tests that we think expose a gap in the spec, we simply add the docfix tag above, along with a description field (which the script will ignore) if it would be helpful to understand why you tagged it. Beyond that, I don't know what other tags would be relevant here, but we should aim to develop a controlled list, so easy to work with the results.

[bdarcus]

Does this make sense @fbennett @adam3smith?

[bdarcus]

In this comment, @fbennett expresses support for also tags and description field, and possibly YAML.

I think the latter should be the longer term goal for the test suite, perhaps borrowing ideas and/or code from jest-csl, but that it's not urgent now, and I'm not the person to do this.

This step would allow for that more extensive refactor later, though.

If you approve, @adam3smith, just merge it?