Add/Fix META.yml files to ease specs to WPT mapping

[tidoust]

I am trying to map specs listed in w3c/browser-specs to their test suites in WPT. Thanks to META.yml files, I can map about 200 specs in that list directly to a WPT folder based on the spec's URL. I can also associate 30 other specs with WPT folders that do not link to a spec explicitly based on the spec's shortname.

There remain 32 cases for which the spec and folder cannot be directly associated because:

1. The URL in the META.yml file is not the right one, either because it targets an outdated version of the spec (e.g. because the spec has migrated from WICG to a working group), because it targets the GitHub repository instead of the spec itself, or simply because it is invalid.
2. There is no spec URL in the META.yml file or there is no META.yml file, and the folder's name does not match the spec's shortname.

This pull request fixes these cases.

I would also be happy to add META.yml files for the 30 folders that do not expose a URL and that I can only map based on their name, so that the mapping uses a consistent mechanism throughout. Should I complete the PR? Here is the list:

List of folders that can only be mapped to a spec based on their name

• badging => Badging API
• content-index => Content Index
• css/css-color-adjust => CSS Color Adjustment Module Level 1
• css/css-scroll-anchoring => CSS Scroll Anchoring Module Level 1
• css/css-size-adjust => CSS Mobile Text Size Adjustment Module Level 1
• custom-state-pseudo-class => Custom State Pseudo Class
• deprecation-reporting => Deprecation Reporting
• intervention-reporting => Intervention Reporting
• is-input-pending => isInputPending
• js-self-profiling => JS Self-Profiling API
• network-error-logging => Network Error Logging
• origin-policy => Origin Policy
• page-lifecycle => Page Lifecycle
• permissions-request => Requesting Permissions
• permissions-revoke => Relinquishing Permissions
• savedata => Save Data API
• serial => Web Serial API
• trusted-types => Trusted Types
• ua-client-hints => User-Agent Client Hints
• web-otp => Web OTP API
• webhid => WebHID API
• webrtc-insertable-streams => WebRTC Insertable Media using Streams
• webrtc-priority => WebRTC Priority Control API
• webrtc-svc => Scalable Video Coding (SVC) Extension for WebRTC
• webtransport => WebTransport
• webxr/anchors => WebXR Anchors Module
• webxr/ar-module => WebXR Augmented Reality Module - Level 1
• webxr/gamepads-module => WebXR Gamepads Module - Level 1
• webxr/hand-input => WebXR Hand Input Module - Level 1
• webxr/hit-test => WebXR Hit Test Module

I note that there exist both a lifecycle and a page-lifecycle folder for the Page Lifecycle specification. Is that intended?

Linked to w3c/browser-specs#201

[foolip]

Awesome, thanks @tidoust!

Since touching many directories will subscribe lots of people, I'll merge this. Please feel free to open another PR for the remaining cases, that would be much appreciated!

[protechq88]

BackgroundSync/META.yml