Rename schema file to data.schema.json and publish it

[foolip]

This will include the schema in the NPM package. The idea is to also
publish it with GitHub releases.

[foolip]

The idea is that this would help with #715. We can publish web-features.schema.json in both the NPM package and the GitHub release. The name of the data files are different (index.json vs. data.json) so matching either of those names would still leave a mismatch in the other place.

[ddbeck]

Ah, so the end-goal here is to export this on the package? import { schema } from "web-features"? In any case, this is fine.

[foolip]

Ah, so the end-goal here is to export this on the package? import { schema } from "web-features"? In any case, this is fine.

This is for @jcscottiii who is using GitHub releases for webstatus.dev, so the goal is to add a file alongside data.json in the GitHub releases. A change in the schema would be a strong clue that something needs updating.

[foolip]

I've sent #1470, and if we do that I think we should call this data.schema.json instead.

[ddbeck]

It'd be nice to update packages/web-features/README.md with an example import statement for this, but I won't block on it. One minor suggestion in a line comment.

[foolip]

I've documented the import as import schema from "web-features/data.schema.json" with { type: "json" } and will merge this now.