Bind an SSH key to a host instead of picking one per connection

A host now names the key it authenticates with, or none, as a field in its
encrypted payload — so the choice follows the host to every machine rather than
being made again each time somebody connects. The per-connection "Use key"
switch it replaces was a stopgap for not having this, and keeping both would
have left two mechanisms answering one question.

This is the first payload schema version bump, and it does not work the obvious
way. A host is written at the *lowest* schema version that can represent it: one
that binds a key is written at 2, one that does not is still written at 1, byte
for byte as it was before the field existed. The version is what makes an older
client refuse to edit an item, so stamping 2 unconditionally would mean
upgrading a single machine and renaming a single host made that host uneditable
on every machine that had not upgraded yet. Confining the cost to the hosts that
actually use the field is the difference between a team noticing a bump and a
team being blocked by one. HostSecretCodec states the rule so the next field
added follows it, and a test pins the version-1 bytes against a literal rather
than against the codec, because the claim is about history: every host already in
every vault has to re-encode to what it encoded before, or the first sync after
an upgrade would push the whole vault as changed.

A binding is an item id, not a copy of the key — a second copy of a private key
is one that goes stale — which means the reference can dangle when the key is
deleted on another machine. Both places that meets are handled the same way, by
refusing rather than falling back:

- Connecting to a host whose key is gone is refused outright. A host somebody
  deliberately set up for key-only access must not quietly start offering a
  password.
- Opening such a host in the editor keeps the binding, selected, labelled as
  missing. The quieter version of the same failure is someone editing the port
  and saving, silently converting the host to password authentication with
  nothing ever having said so.

Two things this found by being falsified:

- The merge was untested for the new field, and "just take the server's value"
  passed the entire suite — a local binding change would have been discarded with
  no conflict recorded. HostSecretMergeTests already had a test written for
  exactly this class of omission; it simply had not been extended.

- Adding a nullable field exposed a defect in HostSecretMerge.Field: it
  short-circuited when the discarded value was null, so the formatter never ran
  for the one case where null is a value rather than an absence, and a field
  whose absence has a name could not report it. Now the formatter always runs,
  and "no key" appears in the conflict log where an empty string used to.

Also fixes eight nullable warnings in SyncEndpointTests left by the server-side
SSH key commit, which had omitted the null-forgiving operator the rest of that
file uses. They were invisible until an unrelated change forced the project to
recompile.

The end-to-end slice now binds its host to its key, so a schema-version-2
payload goes through the real API, the real PostgreSQL and back out on a second
machine.

745 tests green. Zero warnings, dotnet format clean.

src/DodoSSH.Client.App/Views/MainWindow.axaml

@@ -111,8 +111,16 @@
                                VerticalAlignment="Center" />
                   </Border>
                 </StackPanel>
-                <TextBlock Text="{Binding Address}" Classes="hint" FontSize="11"
-                           FontFamily="ui-monospace,Consolas,monospace" />
+                <StackPanel Orientation="Horizontal" Spacing="6">
+                  <TextBlock Text="{Binding Address}" Classes="hint" FontSize="11"
+                             FontFamily="ui-monospace,Consolas,monospace" />
+                  <!--
+                    Which of the two ways this host authenticates. In the list because the password box
+                    below is only relevant to one of them, and an empty box on a key-authenticated host is
+                    otherwise indistinguishable from one somebody forgot to fill in.
+                  -->
+                  <TextBlock Text="{Binding Authentication}" Classes="hint" FontSize="11" />
+                </StackPanel>
               </StackPanel>
             </DataTemplate>
           </ListBox.ItemTemplate>
@@ -128,6 +136,21 @@
             <TextBox Text="{Binding Vault.EditorUsername}" PlaceholderText="username" />
             <TextBox Text="{Binding Vault.EditorNotes}" PlaceholderText="notes" AcceptsReturn="True"
                      Height="60" TextWrapping="Wrap" />
+            <!--
+              Which key this host authenticates with, or a password. Part of the host rather than of the
+              connection, so it follows the host to every machine; a host bound to a key that has since been
+              deleted keeps a placeholder entry here, so that editing the port cannot quietly turn it back
+              into a password host.
+            -->
+            <ComboBox ItemsSource="{Binding Vault.EditorKeyChoices}"
+                      SelectedItem="{Binding Vault.EditorSelectedKey}"
+                      HorizontalAlignment="Stretch">
+              <ComboBox.ItemTemplate>
+                <DataTemplate x:DataType="vm:SshKeyChoice">
+                  <TextBlock Text="{Binding Label}" />
+                </DataTemplate>
+              </ComboBox.ItemTemplate>
+            </ComboBox>
             <CheckBox IsChecked="{Binding Vault.EditorRelayEnabled}"
                       Content="Allow connecting through the server relay" />
             <!--
@@ -237,22 +260,21 @@
             -->
             <TextBox Text="{Binding Vault.ConnectPassword}" PlaceholderText="password (not stored yet)"
                      PasswordChar="•" Width="220" VerticalAlignment="Center"
-                     IsEnabled="{Binding !Vault.UseKeyAuthentication}" />
+                     IsVisible="{Binding !Vault.SelectedHostUsesAKey}" />
             <!--
-              An explicit switch, not "use a key if one is selected". The key list's selection is there to
-              edit and delete keys, and letting it decide how the next connection authenticates would mean
-              clicking a row to rename it changed what Connect does.
+              Hidden rather than disabled for the key case, unlike most of this window. A disabled password
+              box invites the reading that a password is wanted and unavailable; the honest statement for a
+              key-authenticated host is that nothing needs typing, and an absent box says that better than a
+              greyed-out one.
             -->
-            <CheckBox IsChecked="{Binding Vault.UseKeyAuthentication}" Content="Use key"
-                      VerticalAlignment="Center"
-                      ToolTip.Tip="Authenticate with the SSH key selected in the list, instead of a password." />
-            <TextBlock Text="{Binding Vault.SelectedKey.Label, FallbackValue='no key selected'}"
-                       Foreground="#bcd2ea" FontSize="11" VerticalAlignment="Center"
-                       IsVisible="{Binding Vault.UseKeyAuthentication}" />
+            <TextBlock Text="This host authenticates with its SSH key." Classes="hint" FontSize="11"
+                       VerticalAlignment="Center"
+                       IsVisible="{Binding Vault.SelectedHostUsesAKey}" />
             <Button Content="Connect" Command="{Binding Vault.ConnectCommand}"
                     IsEnabled="{Binding !Vault.IsBusy}" VerticalAlignment="Center" />
             <TextBlock Classes="hint" FontSize="11" VerticalAlignment="Center"
-                       Text="Keys are in the vault; passwords are not yet." />
+                       Text="Keys are in the vault; passwords are not yet."
+                       IsVisible="{Binding !Vault.SelectedHostUsesAKey}" />
           </StackPanel>
         </Border>