doc: fix YAML comment opening tags

Several YAML documentation comments incorrectly started with `<!--YAML`
instead of `<!-- YAML`, resulting in their content missing in the
rendered documentation.

PR-URL: #38324
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>

Author: jaydenseric

doc/api/globals.md

@@ -18,7 +18,7 @@ that are part of the JavaScript language itself, which are also globally
 accessible.
 
 ## Class: `AbortController`
-<!--YAML
+<!-- YAML
 added: v15.0.0
 changes:
   - version: v15.4.0

doc/api/packages.md

@@ -291,7 +291,7 @@ import submodule from 'es-module-package/private-module.js';
 ```
 
 ### Subpath imports
-<!--YAML
+<!-- YAML
 added:
   - v14.6.0
   - v12.19.0
@@ -333,7 +333,7 @@ The resolution rules for the imports field are otherwise
 analogous to the exports field.
 
 ### Subpath patterns
-<!--YAML
+<!-- YAML
 added:
   - v14.13.0
   - v12.19.0
@@ -428,7 +428,7 @@ The benefit of patterns over folder exports is that packages can always be
 imported by consumers without subpath file extensions being necessary.
 
 ### Exports sugar
-<!--YAML
+<!-- YAML
 added: v12.11.0
 -->
 
@@ -455,7 +455,7 @@ can be written:
 ```
 
 ### Conditional exports
-<!--YAML
+<!-- YAML
 added:
   - v13.2.0
   - v12.16.0
@@ -630,7 +630,7 @@ The above definitions may be moved to a dedicated conditions registry in due
 course.
 
 ### Self-referencing a package using its name
-<!--YAML
+<!-- YAML
 added:
   - v13.1.0
   - v12.16.0

doc/api/worker_threads.md

@@ -279,7 +279,7 @@ new Worker('process.env.SET_IN_WORKER = "foo"', { eval: true, env: SHARE_ENV })
 ```
 
 ## `worker.setEnvironmentData(key[, value])`
-<!--YAML
+<!-- YAML
 added: v15.12.0
 -->