Updating chromium support for optional data types in the Async Clipboard API

[captainbrosset]

Summary

The Async Clipboard API now supports SVG and custom web formats, in Chromium.

Support for these optional types was documented in BCD in #23134, but I think the chromium versions are incorrect. This PR updates the version numbers based on my findings.

Test results and supporting details

• SVG

  SVG support was added in https://chromium-review.googlesource.com/c/chromium/src/+/5287618 which seems to be 124 according to https://chromiumdash.appspot.com/commit/7380b9043440b808cff97d11f0eb08f704509389.

  This confirms the chromestatus.com entry: https://chromestatus.com/feature/5125790490427392

  So, I think BCD needs to be changed to 124 for both desktop and Android.

• Custom web formats

  Support was added in https://issues.chromium.org/issues/40123727, which covers multiple commits, but the main one (313b28c002f1e552aa5b46094aae405f0fcb456b: "[Clipboard API] Enable Clipboard Web Custom Format API") landed in 104: https://chromiumdash.appspot.com/commit/313b28c002f1e552aa5b46094aae405f0fcb456b

  This is confirmed by the chromestatus.com entry: https://chromestatus.com/feature/5649558757441536

[captainbrosset]

@tayloregivens do you know whether the ClipboardItem.supports() static method is supposed to be supported on Chrome for Android too?

@hamishwillee @Elchi3 I'm wondering if the SVG and custom web format support subfeatures shouldn't be moved to be below the main api.Clipboard entry, rather than nested below the api.ClipboardItem.supports_static entry.
The reason being that supporting those optional formats is a feature of the overal Async Clipboard API, not a specific argument you can pass to the supports() function. Either the browser supports writing/reading SVG data type to the clipboard, or it doesn't.

Thoughts?

[captainbrosset]

@queengooborg I just saw that #23593 was moving non-optional mime-types at the Clipboard API level, whereas the optional mime-types in this PR are at the ClipboardItem API level. Should we align?

[queengooborg]

Considering that support for certain types was implemented before the supports() method was, yes, we should move the types up a level.