refactor: use precomputed status data in baseline generator

[Pixel998]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request?

This change fixes the failing Update baseline workflow. The failure was caused by recent renames in @mdn/browser-compat-data@7.1.16 (see mdn/browser-compat-data#28278). Our generator previously used compute-baseline’s getStatus to query BCD for each compat key from web-features. Because web-features still referenced the old keys, compute-baseline attempted to traverse keys that had been renamed in BCD, causing errors like:

Error: css.properties.position-area.span-x-self-end is unindexable at 'span-x-self-end'.

To resolve this, I switched to the precomputed baseline statuses that now ship with web-features@3.6.0, specifically status.by_compat_key. This removes the need to query BCD at build time, prevents failures from key renames, and avoids version skew between web-features and BCD.

What changes did you make? (Give an overview)

• Removed compute-baseline usage.
• In extractCSSFeatures(), replaced getStatus(featureId, key) with precomputed statuses from web-features: feature.status.by_compat_key[key].

Related Issues

Is there anything you'd like reviewers to focus on?

[fasttime]

LGTM, thanks! I verified that the updated script runs locally with the latest versions of mdn-data and web-features.

[rviscomi]

Ah we just shipped by_compat_key last week and I was planning to reach out to suggest migrating over to it. Glad to see you found it and it's already proving useful!