Update HTML Sanitizer API version info for Fx147

[dipikabh]

Summary

• Reverting version and preference info.
• Adding note for default availability in Nightly.

Context

As discussed with @jakearchibald, this is an update to #28774.

Background

Some notes to capture what's happened in the last few months:

• The correct entry with the flag info was added to browser compat in 138 via Firefox 138/139 adds new Sanitizer API behind flag #26659.
• The flag info was removed and version replaced with Nightly in Firefox Nightly enabled Sanitizer API #28262 (following https://bugzilla.mozilla.org/show_bug.cgi?id=1954437).

Changes in this PR

• The feature has been available behind the flag since 138, so this PR restores that flag info. We can change 138 to 148 and remove the preference info once the feature is available in stable release in 148.
• Since it's available by default in Nightly, I've added a note for this. (Do we have other ways to indicate this type of situation?)

Related docs

Channel-wise details are documented on the Experimental features page.
147 makes it available by default in Beta and Developer Edition; but we don't mention those channels in BCD, only the stable release and Nightly.

/cc @hamishwillee for awareness.

[github-actions]

Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs).

[hamishwillee]

I am opposed to this.

At this stage in the release cycle BCD might set the feature as "preview" to capture that this is in nightly only. However if you put as 148 the toolchain automatically shows data as preview until the release goes live.

What we don't do once something is in preview is keep all the old flag and version information.

[dipikabh]

@hamishwillee in that case, we go with Jake's update in #28774? I had thought we might want to keep the preference info.

The version previous to his change was "147", not "Nightly", which is what was causing the confusion. In 147 stable, it is still behind the flag.

[hamishwillee]

Yes, there was nothing wrong with Jake's PR from a BCD perspective - #28774
That should render as preview now, and change to 148 when that becomes the release.
If not, then there is an infrastructure problem AIUI.

As noted, you could equally well modify from "148" to "preview". That would also be correct. But you wouldn't bother so close to v148 becoming a release.

PS I understand why you want to keep the preference info - it just isn't a BCD "way of working" once things reach preview.

[Elchi3]

I agree with Hamish.

[dipikabh]

Since we're still more than a month away from Fx148, to me it was unsettling that with the version set as "148", the compat table suggests that the feature is coming in a future release, without any indication that it is already available in Nightly. Or behind a flag in stable.

I guess I missed reading the legend more closely, which does say "In development. Supported in a pre-release version."

it just isn't a BCD "way of working" once things reach preview.
Appreciate the clarification!

I'll defer to the judgement from you both, thank you! Closing this now.