Consistency linter: needs to compare version_removed version, not just truthiness

[foolip]

The lint already disallows declaring a sub-feature supported when the parent feature is set to false, or declaring a sub-feature shipped earlier than a parent feature. However, it doesn't catch cases with ranges. This is the case where I noticed it:

Parent feature:

browser-compat-data/api/Touch.json

Lines 17 to 26 in ea482a5

	"firefox": [
	{
	"version_added": "52"
	},
	{
	"version_added": "18",
	"version_removed": "24",
	"notes": "Removed in <a href='https://bugzil.la/888304'>bug 888304</a> due to web compatibility issues."
	}
	],

Sub-feature:

browser-compat-data/api/Touch.json

Lines 73 to 75 in ea482a5

	"firefox": {
	"version_added": "46"
	},

This should fail the lint, because in Firefox 46 the parent feature wasn't enabled.

[foolip]

Another case of this is shared workers:

browser-compat-data/api/SharedWorker.json

Lines 155 to 161 in ebb58c1

	"safari": {
	"version_added": "15",
	"notes": [
	"Nested workers support was introduced in Safari 15.5.",
	"Script loading in nested workers was introduced in Safari 16.4."
	]
	},

That should fail the lint because Safari 15 isn't supported by the parent feature:

browser-compat-data/api/SharedWorker.json

Lines 93 to 101 in ebb58c1

	"safari": [
	{
	"version_added": "16"
	},
	{
	"version_added": "5",
	"version_removed": "7"
	}
	],

I stumbled on this in web-platform-dx/web-features#1294.