fix: operator precedence bug in version display and settings default mismatch

- Options.xaml.cs: Add parentheses around null-coalescing fallback so
  '?? 2.0.0' actually triggers when Version is null. Without parens,
  string concatenation always produces non-null, making fallback dead code.
- Settings.settings: Change BitmapEffects default from True to False to
  match Settings.Designer.cs. Prevents silent flip if designer regenerates
  the file, preserving GPU auto-detection intent.

Found by Opus code review.

Author: shanselman

Options.xaml.cs

@@ -31,7 +31,7 @@ protected override void OnActivated(EventArgs e)
             base.OnActivated(e);
             Mouse.Capture(this, CaptureMode.SubTree);
             // Get version from assembly
-            versionLabel.Text = "Version " + System.Reflection.Assembly.GetExecutingAssembly().GetName().Version?.ToString() ?? "2.0.0";
+            versionLabel.Text = "Version " + (System.Reflection.Assembly.GetExecutingAssembly().GetName().Version?.ToString() ?? "2.0.0");
         }
 
         protected override void OnDeactivated(EventArgs e)

Properties/Settings.settings

@@ -9,9 +9,9 @@
       <Value Profile="(Default)">True</Value>
     </Setting>
     <Setting Name="BitmapEffects" Type="System.Boolean" Scope="User">
-      <Value Profile="(Default)">True</Value>
+      <Value Profile="(Default)">False</Value>
     </Setting>
-    <Setting Name="ClearAfter" Type="System.Int32" Scope="User">
+    <Setting Name="ClearAfter"Type="System.Int32" Scope="User">
       <Value Profile="(Default)">35</Value>
     </Setting>
     <Setting Name="MouseDraw" Type="System.Boolean" Scope="User">