feat: lift the client's concurrency ceiling from ~15 peers to 1024

The client had never been driven at scale. A stress harness that mixes
searches, downloads, uploads and browses against a local soulfind found four
ceilings, three of which lose work silently rather than merely being slow.

Peers were capped at one per core. ActorSystem ran each actor's whole lifetime
as one job on a fixed-size ThreadPool, and actor loops block until stopped, so
the pool acted as a semaphore: past the cap an actor never started, never
connected and never errored, and uploads stopped working entirely. The pool had
exactly one consumer and every job it received was non-terminating, so it is
gone; actors get their own thread.

TransferResponse raced the bookkeeping it depends on. It was sent straight back
to the peer while UpdateDownloadTokens was still queued for the client loop —
but the response is what invites the peer's file connection, and that connection
is matched by token. Under load the client loop lost, the file connection
matched nothing, and the download sat on Queued forever. The response now goes
out after the token is recorded.

Download tokens were md5(filename) truncated to 20 bits, and the store deletes
every entry matching a token, so two downloads sharing one destroyed each other
— which fetching the same filename from two peers does every time. They now
come from a counter.

Port 0 from GetPeerAddress means the server does not know where a user listens.
It was cached and dialled, and the upload waiting on it was dropped. It is no
longer cached or served against; the connect attempt stays, because its failure
is what makes an unreachable peer fall back to server brokering.

Mixed profile at 1024 peers: 512/512 downloads, 256/256 uploads, 400-850 MiB/s
in ~7s, against 71/96 downloads at 7.9 MiB/s and a 60s timeout before.

soulseek-rs-lib/src/client/mod.rs

@@ -19,7 +19,7 @@ use crate::{
     },
     shares::Shares,
     types::{Download, Search, SearchResult},
-    utils::{lock::RwLockExt, md5, thread_pool::ThreadPool},
+    utils::{lock::RwLockExt, md5},
 };
 use std::{
     collections::{HashMap, HashSet},
@@ -65,13 +65,25 @@ fn next_connect_token() -> u32 {
 }
 
 /// Upload tokens are minted in the high half of the space so they never collide
-/// with download tokens (md5-derived, always < 2^20).
+/// with download tokens, which are always < 2^31.
 static NEXT_UPLOAD_TOKEN: AtomicU32 = AtomicU32::new(0x8000_0000);
 
 fn next_upload_token() -> u32 {
     NEXT_UPLOAD_TOKEN.fetch_add(1, Ordering::Relaxed)
 }
 
+/// Source of download tokens, kept in the low half of the space.
+///
+/// A counter, not a hash of the filename: the download store is keyed by token
+/// and removes every entry matching one, so any two downloads sharing a token
+/// destroy each other — and the same filename from two peers is an ordinary
+/// thing to queue.
+static NEXT_DOWNLOAD_TOKEN: AtomicU32 = AtomicU32::new(1);
+
+fn next_download_token() -> u32 {
+    NEXT_DOWNLOAD_TOKEN.fetch_add(1, Ordering::Relaxed) % 0x8000_0000
+}
+
 /// A file we have agreed to serve to a peer, awaiting their TransferResponse.
 struct UploadJob {
     downloader: String,
@@ -386,11 +398,7 @@ impl ClientContext {
 impl ClientContext {
     #[must_use]
     pub fn new() -> Self {
-        let max_threads =
-            thread::available_parallelism().map_or(8, std::num::NonZero::get);
-
-        let thread_pool = Arc::new(ThreadPool::new(max_threads));
-        let actor_system = Arc::new(ActorSystem::new(thread_pool));
+        let actor_system = Arc::new(ActorSystem::new());
 
         Self {
             peer_registry: None,