Add caniuse links where the IDs are different

Follow-up to web-platform-dx#3300
which only covered cases of (hyphenless) IDs matching.

The starting point was a bunch of changes suggested by Gemini, asked to
identify features that might be the same. The suggests were reviewed and
about half of them are good. Comments were added where the features
almost match but not quite.

The description of execCommand() is also updated to reflect that the
method sits on document, which is baked into the caniuse ID.

Author: foolip

features/appearance.yml

@@ -1,6 +1,7 @@
 name: appearance
 description: "The `appearance` CSS property controls the appearance of form controls. Using `appearance: none` disables any default native appearance and allows the elements to be styled with CSS."
 spec: https://drafts.csswg.org/css-ui-4/#appearance-switching
+caniuse: css-appearance
 group: css
 compat_features:
   - css.properties.appearance

features/capture-stream-audio-video.yml

@@ -1,6 +1,8 @@
 name: captureStream() for <audio> and <video>
 description: The `captureStream()` method for `<audio>` and `<video>` elements returns a `MediaStream` for the media element's content. You can use this to record media or send it elsewhere, such as a canvas or WebRTC connection.
 spec: https://w3c.github.io/mediacapture-fromelement/#html-media-element-media-capture-extensions
+# https://caniuse.com/mediacapture-fromelement is not linked because it covers
+# <audio>, <video>, and <canvas>, which are split here in web-features.
 group: media-elements
 compat_features:
   - api.HTMLMediaElement.captureStream

features/capture-stream-canvas.yml

@@ -6,6 +6,8 @@ description: The `captureStream()` method for `<canvas>` elements returns a `Med
 #
 # See also: https://bugzil.la/1231131
 spec: https://w3c.github.io/mediacapture-fromelement/#html-canvas-element-media-capture-extensions
+# https://caniuse.com/mediacapture-fromelement is not linked because it covers
+# <audio>, <video>, and <canvas>, which are split here in web-features.
 group: canvas
 status:
   compute_from: api.HTMLCanvasElement.captureStream

features/data-urls.yml

@@ -1,6 +1,7 @@
 name: Data URLs
 description: Data URLs are URLs that start with the `data:` scheme and which directly contain data rather than point to remote resources.
 spec: https://www.rfc-editor.org/rfc/rfc2397
+caniuse: datauri
 status:
   compute_from: http.data-url
 compat_features:

features/execcommand.yml

@@ -1,6 +1,7 @@
 name: execCommand()
-description: The `execCommand()` method reads and writes from the clipboard and performs editing commands on editable text, such as changing the font name or style. Related methods check whether commands are supported, enabled, or applied.
+description: The `document.execCommand()` method reads and writes from the clipboard and performs editing commands on editable text, such as changing the font name or style. Related methods check whether commands are supported, enabled, or applied.
 spec: https://w3c.github.io/editing/docs/execCommand/
+caniuse: document-execcommand
 group: clipboard
 discouraged:
   according_to:

features/hsts.yml

@@ -1,6 +1,7 @@
 name: HTTP Strict Transport Security
 description: The `Strict-Transport-Security` HTTP response header informs browsers that the site should only be accessed using HTTPS, and that any future attempts to access it using HTTP should automatically be converted to HTTPS. Also known as HSTS.
 spec: https://www.rfc-editor.org/rfc/rfc6797
+caniuse: stricttransportsecurity
 group: security
 compat_features:
   - http.headers.Strict-Transport-Security

features/mediastream-recording.yml

@@ -1,6 +1,7 @@
 name: MediaStream recording
 description: The `MediaRecorder` API captures data generated by `MediaStream` or `HTMLMediaElement` objects for analysis, processing, or saving to disk. Also known as the Media Recording API.
 spec: https://w3c.github.io/mediacapture-record/
+caniuse: mediarecorder
 status:
   compute_from:
     - api.MediaRecorder.isTypeSupported_static

features/navigation-timing.yml

@@ -1,6 +1,7 @@
 name: Navigation timing
 description: The `navigation` performance entry and the `PerformanceNavigationTiming` API measures navigation events, such as loading time or the number of redirects.
 spec: https://w3c.github.io/navigation-timing/
+caniuse: nav-timing
 group: performance
 status:
   compute_from: api.PerformanceNavigationTiming

features/network-information.yml

@@ -1,6 +1,7 @@
 name: Network Information
 description: The `navigator.connection` API provides information about the network connection a device is using and fires events when the connection type changes.
 spec: https://wicg.github.io/netinfo/
+caniuse: netinfo
 compat_features:
   - api.Navigator.connection
   - api.NetworkInformation

features/serial.yml

@@ -1,6 +1,7 @@
 name: Web serial
 description: The `navigator.serial` API communicates with devices over serial ports, such as microcontrollers.
 spec: https://wicg.github.io/serial/
+caniuse: web-serial
 status:
   compute_from: api.Navigator.serial
 compat_features: