fix(auth): a new recovery phrase takes the password too

password.setRecoveryKeys took a session and a TOTP code alone, so a phone
signed in with its authenticator beside it could set a phrase of its
holder's own and, through the phrase's reset, a new password, never
knowing the old one. It now takes the old password's SRP proof (from
beginChange, the caller's own) and a TOTP or recovery code, as changing
the password does: one owner proof for both (_proveOwner), forwarded by
members, asked for in the account section's New recovery phrase.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>

packages/halkyon_base_server/test/integration/register/member_test.dart

@@ -407,7 +407,11 @@ final class _Register implements AccountRegister {
   Future<void> setRecoveryKeys(
     Session session, {
     required UuidValue person,
-    required String code,
+    required UuidValue challenge,
+    required ByteData clientValue,
+    required ByteData clientProof,
+    String? totpCode,
+    String? recoveryCode,
     required WrappedKeys recoveryKeys,
   }) => _answer('setRecoveryKeys', () {});