Release web-features as GitHub release with JSON artefact

[foolip]

We can probably copy the approach that BCD uses, with an attached data.json.
https://github.com/mdn/browser-compat-data/releases/tag/v5.5.15

Requested by @jcscottiii.

[foolip]

I have manually made a release in the shape I think we should automate:
https://github.com/web-platform-dx/web-features/releases/tag/v0.6.0

[ddbeck]

I think we now need two artifacts.

The first is as described, including data.json without the npm package wrapper on GitHub releases.

The second would be a more comprehensive file containing the single-key status results of getStatus() for each feature. This has come by MDN's request, since they don't want a JS dependency for this data.

For the latter, I think we'll need some extension or variation on the schema for the purposes of this one file. Something like:

status:
  baseline: false
  support:
    chrome: "95"
    edge: "95"
  by_compat_feature:
    api.example.method:
      status:
        baseline: false
        support:
          chrome: "95"
          edge: "95"
    # etc.

[foolip]

That looks good I think, in particular that BCD keys are grouped under features, so that we have the option of having the status of a specific BCD key differ depending on the feature it's part of in the future. This depends on #1173 of course.

[ddbeck]

This is now done automatically as of #1559. I think this is well and truly done now. Closing as complete.