Bump prettier from 3.5.3 to 3.6.0 (#2490)

Author: dependabot[bot]

docs/reviewing-bcd-changes.md

@@ -20,14 +20,12 @@ The `update-bcd.js` script works as follows:
 These errors are worth looking out for:
 
 - False negatives, where a test fails to detect support. This results in either an incorrect `false` or support actually going back further than inferred. Common causes are:
-
   - Missing [interface objects](https://webidl.spec.whatwg.org/#interface-object). For example, `crypto.subtle` was shipped long before the `SubtleCrypto` interface was [exposed](https://webkit.org/b/165629) in some browsers. Missing interface objects was common in the past, especially for events, but is quite _uncommon_ for APIs introduced after ~2020. See [#7963](https://github.com/mdn/browser-compat-data/pull/7963), [#7986](https://github.com/mdn/browser-compat-data/pull/7986) and [#10837](https://github.com/mdn/browser-compat-data/pull/10837) for examples.
   - [Attributes](https://webidl.spec.whatwg.org/#es-attributes) weren't on the prototypes in some older browsers, for example [before Chrome 43](https://github.com/mdn/browser-compat-data/issues/7843). See [#6568](https://github.com/mdn/browser-compat-data/pull/6568#discussion_r479039982) for an example.
 
   To guard against this, follow the link to the test and expand the code. A simple `'propertyName' in InterfaceName` test can yield false negatives, so an _instance_ of the type should be created and tested using the [custom tests](https://github.com/openwebdocs/mdn-bcd-collector/blob/main/custom-tests.yaml) mechanism. Ask for this when reviewing, you don't need to create the tests yourself.
 
 - Consistency with other parts of the same feature. Does it seem plausible that the feature was introduced earlier or later than other parts? Examples of consistency to look for:
-
   - Support for `navigator.gpu` implies support for the `GPU` interface, because `navigator.gpu` is an instance of that interface.
   - Support for `audioContext.createPanner()` implies support for `PannerNode`, because that is the return type.
   - Support for `AnalyserNode` implies support for `AudioNode`, because `AnalyserNode` inherits from `AudioNode`.

package-lock.json

@@ -129,7 +129,7 @@
     "node-fetch": "3.3.2",
     "nodemon": "3.1.10",
     "open-cli": "8.0.0",
-    "prettier": "3.5.3",
+    "prettier": "3.6.0",
     "puppeteer": "24.10.2",
     "sass": "1.89.2",
     "selenium-webdriver": "4.33.0",

package.json

@@ -1913,8 +1913,7 @@ describe("BCD updater", () => {
         userAgent: firefox92UaString,
       };
       const expectedBcd = clone(initialBcd);
-      expectedBcd.api.AbortController.__compat.support.firefox.version_added =
-        false;
+      expectedBcd.api.AbortController.__compat.support.firefox.version_added = false;
 
       const sm = getSupportMatrix([report], initialBcd.browsers, []);