Merge: the formatter's pass over the accessibility test

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

ui/dr-ui/tests/ui_controls_are_accessible.rs

@@ -57,12 +57,20 @@ const PROMISES: &[Promise] = &[
     Promise {
         file: "widgets.slint",
         component: "Button",
-        properties: &["accessible-role", "accessible-label", "accessible-action-default"],
+        properties: &[
+            "accessible-role",
+            "accessible-label",
+            "accessible-action-default",
+        ],
     },
     Promise {
         file: "widgets.slint",
         component: "IconButton",
-        properties: &["accessible-role", "accessible-label", "accessible-action-default"],
+        properties: &[
+            "accessible-role",
+            "accessible-label",
+            "accessible-action-default",
+        ],
     },
     Promise {
         file: "widgets.slint",
@@ -144,9 +152,8 @@ fn read(path: &Path) -> String {
 /// file": the point is that a property found for `Button` really is inside
 /// `Button` and not inside the component below it.
 fn component_body<'a>(source: &'a str, name: &str) -> Option<&'a str> {
-    let header_starts = |line: &str| {
-        line.starts_with("component ") || line.starts_with("export component ")
-    };
+    let header_starts =
+        |line: &str| line.starts_with("component ") || line.starts_with("export component ");
 
     let mut start = None;
     for (offset, line) in line_offsets(source) {