Rename hover memory layout config key

crates/rust-analyzer/src/config.rs

@@ -316,7 +316,7 @@ config_data! {
         /// Use markdown syntax for links on hover.
         hover_links_enable: bool = "true",
         /// Whether to show memory layout data on hover.
-        hover_memory_layout_enable: bool = "true",
+        hover_memoryLayout_enable: bool = "true",
 
         /// Whether to enforce the import granularity setting for all files. If set to false rust-analyzer will try to keep import styles consistent per file.
         imports_granularity_enforce: bool              = "false",
@@ -1474,7 +1474,7 @@ impl Config {
     pub fn hover(&self) -> HoverConfig {
         HoverConfig {
             links_in_hover: self.data.hover_links_enable,
-            memory_layout: self.data.hover_memory_layout_enable,
+            memory_layout: self.data.hover_memoryLayout_enable,
             documentation: self.data.hover_documentation_enable,
             format: {
                 let is_markdown = try_or_def!(self

docs/user/generated_config.adoc

@@ -423,7 +423,7 @@ Whether to show keyword hover popups. Only applies when
 --
 Use markdown syntax for links on hover.
 --
-[[rust-analyzer.hover.memory.layout.enable]]rust-analyzer.hover.memory.layout.enable (default: `true`)::
+[[rust-analyzer.hover.memoryLayout.enable]]rust-analyzer.hover.memoryLayout.enable (default: `true`)::
 +
 --
 Whether to show memory layout data on hover.

editors/code/package.json

@@ -959,7 +959,7 @@
                     "default": true,
                     "type": "boolean"
                 },
-                "rust-analyzer.hover.memory.layout.enable": {
+                "rust-analyzer.hover.memoryLayout.enable": {
                     "markdownDescription": "Whether to show memory layout data on hover.",
                     "default": true,
                     "type": "boolean"