Add linter to make sure statuses have consistent inheritance

[saschanaz]

A checklist to help your pull request get merged faster:

• [x] Summarize your changes
• [ ] Data: link to resources that verify support information (such as browser's docs, changelogs, source control, bug trackers, and tests)
• [ ] Data: if you tested something, describe how you tested with details like browser and version
• [ ] Review the results of the linter and fix problems reported (If you need help, please ask in a comment!)
• [x] Link to related issues or pull requests, if any: closes #7348, https://github.com/mdn/browser-compat-data/pull/15932

[foolip]

Right, also it shouldn't be possible to have a standard feature as a child of a non-standard feature. So all 3 statuses should be possible to have similar lints for.

[saschanaz]

Got a lot more after including experimental status check, so splitting this too.

[github-actions[bot]]

This pull request has merge conflicts that must be resolved before we can merge this.

[github-actions[bot]]

This pull request has merge conflicts that must be resolved before we can merge this.

[github-actions[bot]]

This pull request has merge conflicts that must be resolved before we can merge this.

[queengooborg]

Looks like this needs to be formatted, could you run a formatter real quick to see what needs to be done to make this linter pass?

[saschanaz]

(https://github.com/mdn/browser-compat-data/pull/15932 exists for this)

[github-actions[bot]]

This pull request has merge conflicts that must be resolved before it can be merged.

[github-actions[bot]]

This pull request has merge conflicts that must be resolved before it can be merged.

[saschanaz]

I don't think I'll merge repeatedly only to be replaced by others, closing.