fix: reliable first-message send, QR routing, auto-lock recovery

Fixes reported by testers and found in an app review:

- First message right after install no longer fails. Before the app
  finished registering with the relay, the outgoing message could crash on
  a null delivery address. The profile field is now optional and the send
  path throws a clear "still connecting, try again shortly" error while
  registration completes in the background.
- The QR code and share link now appear only once the delivery address is
  ready. Previously a link generated before the first connection lacked
  routing, so the other side could not send the first message. The screen
  now shows a connecting state and reactively swaps in the QR when ready.
- Incomplete contact links are rejected on import instead of failing at
  first send, with a clear prompt to ask for a fresh link.
- Auto-lock no longer silences the app: after locking and unlocking,
  messaging is restarted (it previously stayed dead until app restart).
- Group messages are marked failed on a non-per-member send error instead
  of hanging in the "sending" state forever.
- Hardened the relay client against a rare duplicate connection when
  toggling Tor or locking mid-connect, and fromShareString now rejects a
  delivery address of the wrong length.
- Pin unifiedpush below 6.2.0 to drop the webcrypto dependency (its native
  framework lacks LC_ENCRYPTION_INFO and blocked the iOS upload).
- Skip Android release lint (network dependency check hangs on the build
  host and adds no value for a Flutter app).

app/lib/l10n/generated/app_localizations_de.dart

@@ -277,6 +277,14 @@ class AppLocalizationsDe extends AppLocalizations {
   String get errorRelayUnavailable =>
       'Relay nicht erreichbar (Sender-Zertifikat)';
 
+  @override
+  String get errorNotYetRegistered =>
+      'Šepot verbindet sich noch mit dem Relay — versuch es gleich noch einmal.';
+
+  @override
+  String get errorContactLinkIncomplete =>
+      'Dieser Link ist unvollständig — die andere Person hat ihn erstellt, bevor sie verbunden war. Bitte sie um einen neuen sepot://-Link.';
+
   @override
   String errorAttachmentTooLarge(int maxMb) {
     return 'Anhang ist zu groß (max. $maxMb MB)';
@@ -1067,6 +1075,13 @@ class AppLocalizationsDe extends AppLocalizations {
   @override
   String get qrShareTitle => 'Meine Šepot-ID';
 
+  @override
+  String get qrShareConnectingTitle => 'Verbinde mit dem Relay…';
+
+  @override
+  String get qrShareConnectingBody =>
+      'Dein QR-Code und Link erscheinen, sobald sich Šepot zum ersten Mal verbindet. Einen Moment — es dauert nur ein paar Sekunden.';
+
   @override
   String get qrIdentityNotFound => 'Identität nicht gefunden';