Reconsideration: allow `webauthn-public-key-easy` to regress to limited availability

[ddbeck]

In #3991, I'm putting a hold on webauthn-public-key-easy (source, dist) from regressing. We should decide how to handle this status change.

Background

In mdn/browser-compat-data#29458, Safari's implementation of AuthenticatorAttestationResponse: getPublicKey() was marked as partial due to reported missing support for certain algorithms.

This was filed with WebKit as bug 312081. It's currently unconfirmed.

The spec says support for the missing algorithms are required with "must" language.

In #3991, this partial cascaded to the status for the webauthn-public-key-easy feature. At the time the feature was frozen, this feature was Baseline low.

status:
  baseline: low
  baseline_low_date: 2023-10-24
  support:
    chrome: "85"
    chrome_android: "85"
    edge: "85"
    firefox: "119"
    firefox_android: "119"
    safari: "16"
    safari_ios: "16"

Without the status freeze this feature would regress to limited availability. Without the partial, this feature would have advanced to Baseline high.

Options

• Regress. Agree that the bug is a serious lack of support, undo the editorial override, and allow the regression to happen.
• Advance with changes upstream to unmark this partial (needs support from BCD maintainers too).
• Advance with a compute_from ignoring webauthn-public-key-easy. Silently ignore BCD. Note that this does not override per-key statuses.
• Hold. Leave override in place. Silently ignore BCD. Note that this does not override per-key statuses. We should choose this option if we cannot come to an agreement about other solutions.