fix(bcd): Prioritize current support using a ranking system

[danielhjacobs]

Summary

Fixes #5945

Problem

Current support is defined as the most recent support item:

yari/client/src/document/ingredients/browser-compatibility-table/feature-row.tsx

Line 139 in e93d4a5

const currentSupport = getFirst(support);

However, look at innerHeight for Firefox on https://developer.mozilla.org/en-US/docs/Web/API/Window/innerHeight#browser_compatibility. It's had full support since version 1, but a removed note in effect from version 4-24. Because that item is newer and was removed, it looks like it has no support.

Solution

Rank the support items as follows:

• Active items (version_removed === null)
  • Full support without limitation (i.e. only version_added)
  • Full support with only version_added and notes
  • Full support with altname/prefix
  • Partial support
  • Support with flags
  • No support
• Inactive items (version_removed !== null)

---

Screenshots

Before

After

[danielhjacobs]

I've done the prioritization of support. As was expected, it is complex. If there are preferences for rewriting things a certain way, let me know. I did it with many return statements so that in most cases, not all the finds need to be run for each cell. I could have done a let with a return at the end, but I tend to like returning early for efficiency. Returning early also lets the checks be less complex, since things that would have been caught by an earlier find don't need to be rechecked that they don't exist in a later find.

[caugner]

Looks good overall, just a few nits.