ChorusHubServerInfo uses static field for discovered server, causing state leakage between instances

ChorusHubServerInfo stores its discovered server in a static field (src/LibChorus/ChorusHub/ChorusHubServerInfo.cs):

private static ChorusHubServerInfo _chorusHubServerInfo;

All code paths that call FindServerInformation() — including SyncStartControl.CheckNetworkStatusAndUpdateUI — share this single instance. In test scenarios or when multiple independent sync sessions run in the same process, a stale server discovered by one session leaks into another. The existence of ClearServerInfoForTests() as a public workaround confirms this is a known design issue:

public static void ClearServerInfoForTests()
{
    _chorusHubServerInfo = null;
}

Fix: Convert _chorusHubServerInfo to an instance member, or restructure discovery to use a properly scoped pattern that does not share state across unrelated sessions.

Found via DeepWiki.

Start in src/LibChorus/ChorusHub/ChorusHubServerInfo.cs and trace FindServerInformation(), including its use from SyncStartControl.CheckNetworkStatusAndUpdateUI. Review how ClearServerInfoForTests() is used and identify the appropriate lifetime for discovered server information. Done means independent sync sessions no longer share stale discovery state, with affected callers and tests updated accordingly.