update rust-analyzer to 2025-11-10

[sublimelsp-app]

Update rust-analyzer from 2025-08-25 to 2025-11-10 (see all changes).

[github-actions]

Following are the settings schema changes between tags 2025-08-25 and 2025-11-10. Make sure that those are reflected in LSP-rust-analyzer.sublime-settings and sublime-package.json files.

--- /dev/fd/63	2025-11-11 09:26:12.367920233 +0000
+++ /dev/fd/62	2025-11-11 09:26:12.367920233 +0000
@@ -1273,6 +1273,16 @@
     }
   },
   {
+    "title": "Goto Implementations",
+    "properties": {
+      "rust-analyzer.gotoImplementations.filterAdjacentDerives": {
+        "markdownDescription": "If this is `true`, when \"Goto Implementations\" and in \"Implementations\" lens, are triggered on a `struct` or `enum` or `union`, we filter out trait implementations that originate from `derive`s above the type.",
+        "default": false,
+        "type": "boolean"
+      }
+    }
+  },
+  {
     "title": "Highlight Related",
     "properties": {
       "rust-analyzer.highlightRelated.branchExitPoints.enable": {
@@ -1655,19 +1665,30 @@
         "markdownDescription": "How imports should be grouped into use statements.",
         "default": "crate",
         "type": "string",
-        "enum": [
-          "preserve",
-          "crate",
-          "module",
-          "item",
-          "one"
-        ],
-        "enumDescriptions": [
-          "Do not change the granularity of any imports and preserve the original structure written by the developer.",
-          "Merge imports from the same crate into a single use statement. Conversely, imports from different crates are split into separate statements.",
-          "Merge imports from the same module into a single use statement. Conversely, imports from different modules are split into separate statements.",
-          "Flatten imports so that each has its own use statement.",
-          "Merge all imports into a single use statement as long as they have the same visibility and attributes."
+        "anyOf": [
+          {
+            "enum": [
+              "crate",
+              "module",
+              "item",
+              "one"
+            ],
+            "enumDescriptions": [
+              "Merge imports from the same crate into a single use statement. Conversely, imports from different crates are split into separate statements.",
+              "Merge imports from the same module into a single use statement. Conversely, imports from different modules are split into separate statements.",
+              "Flatten imports so that each has its own use statement.",
+              "Merge all imports into a single use statement as long as they have the same visibility and attributes."
+            ]
+          },
+          {
+            "enum": [
+              "preserve"
+            ],
+            "enumDescriptions": [
+              "Deprecated - unless `enforceGranularity` is `true`, the style of the current file is preferred over this setting. Behaves like `item`."
+            ],
+            "deprecated": true
+          }
         ]
       }
     }
@@ -1858,6 +1879,16 @@
   {
     "title": "Inlay Hints",
     "properties": {
+      "rust-analyzer.inlayHints.expressionAdjustmentHints.disableReborrows": {
+        "markdownDescription": "Disable reborrows in expression adjustments inlay hints.\n\nReborrows are a pair of a builtin deref then borrow, i.e. `&*`. They are inserted by the compiler but are mostly useless to the programmer.\n\nNote: if the deref is not builtin (an overloaded deref), or the borrow is `&raw const`/`&raw mut`, they are not removed.",
+        "default": true,
+        "type": "boolean"
+      }
+    }
+  },
+  {
+    "title": "Inlay Hints",
+    "properties": {
       "rust-analyzer.inlayHints.expressionAdjustmentHints.enable": {
         "markdownDescription": "Show inlay hints for type adjustments.",
         "default": "never",
@@ -1991,7 +2022,7 @@
     "title": "Inlay Hints",
     "properties": {
       "rust-analyzer.inlayHints.maxLength": {
-        "markdownDescription": "Maximum length for inlay hints. Set to null to have an unlimited length.",
+        "markdownDescription": "Maximum length for inlay hints. Set to null to have an unlimited length.\n\n**Note:** This is mostly a hint, and we don't guarantee to strictly follow the limit.",
         "default": 25,
         "type": [
           "null",
@@ -2374,6 +2405,19 @@
     }
   },
   {
+    "title": "Profiling",
+    "properties": {
+      "rust-analyzer.profiling.memoryProfile": {
+        "markdownDescription": "The path where to save memory profiling output.\n\n**Note:** Memory profiling is not enabled by default in rust-analyzer builds, you need to build\nfrom source for it.",
+        "default": null,
+        "type": [
+          "null",
+          "string"
+        ]
+      }
+    }
+  },
+  {
     "title": "References",
     "properties": {
       "rust-analyzer.references.excludeImports": {
@@ -2425,7 +2469,7 @@
       "rust-analyzer.runnables.extraTestBinaryArgs": {
         "markdownDescription": "Additional arguments to be passed through Cargo to launched tests, benchmarks, or\ndoc-tests.\n\nUnless the launched target uses a\n[custom test harness](https://doc.rust-lang.org/cargo/reference/cargo-targets.html#the-harness-field),\nthey will end up being interpreted as options to\n[`rustc`’s built-in test harness (“libtest”)](https://doc.rust-lang.org/rustc/tests/index.html#cli-arguments).",
         "default": [
-          "--show-output"
+          "--nocapture"
         ],
         "type": "array",
         "items": {
@@ -2485,6 +2529,16 @@
         "type": "boolean"
       }
     }
+  },
+  {
+    "title": "Semantic Highlighting",
+    "properties": {
+      "rust-analyzer.semanticHighlighting.comments.enable": {
+        "markdownDescription": "Use semantic tokens for comments.\n\nIn some editors (e.g. vscode) semantic tokens override other highlighting grammars.\nBy disabling semantic tokens for comments, other grammars can be used to highlight\ntheir contents.",
+        "default": true,
+        "type": "boolean"
+      }
+    }
   },
   {
     "title": "Semantic Highlighting",