fix(session): don't release the session on a SOCKS5 Reconnect

Regression from e67f0b9, shipped in 3.3.7.

Reconnect repairs an orphaned proxy by tearing the runtime down and
re-attaching to the session the device already holds. It does that
through SessionTimer.disconnect(), which e67f0b9 taught to hand the
session back to the server - so it destroyed the very session the
following connect(resume: true) then asked for. Unawaited, so it raced:
the resume either found the session already gone or removed moments
later, surfacing as "Session not activated".

disconnect() now takes release, and the Reconnect path passes false.
Every other caller still hands the session back.

Narrow in practice: SOCKS5 mode only, only the Settings Reconnect
button, and the main-screen connect was unaffected because it mints a
new session anyway.

Co-Authored-By: Claude Opus 5 <[email protected]>

test/session_lifecycle_regression_test.dart

@@ -131,4 +131,22 @@ void main() {
       reason: 'exactly one call site',
     );
   });
+
+  test('SOCKS5 Reconnect re-attaches instead of handing the session back', () {
+    final timer = File('lib/logic/session_timer.dart').readAsStringSync();
+    final mode =
+        File('lib/screens/settings/in_settings/connection_mode.dart')
+            .readAsStringSync();
+
+    // Reconnect repairs an orphaned proxy by re-attaching to the session the
+    // device already holds. Releasing it on the way out would destroy the very
+    // session the follow-up connect(resume: true) then asks for.
+    expect(timer, contains('bool release = true'));
+    expect(timer, contains('if (release) unawaited(HivemindService.releaseSession())'));
+    expect(mode, contains('timer.disconnect(release: false)'));
+    expect(mode, contains('vpn.connect(resume: true)'));
+
+    // And it must not hand back a second support top-up for the same session.
+    expect(mode, contains('timer.start(resetSupportClaim: false)'));
+  });
 }