Fix: transient HttpRequestException resets stabilization state in DockerApiClient

[Copilot]

The HttpRequestException handler in GetAllContainerHostPortsAsync was resetting lastSeenId = null and isFirstPoll = false, causing the next successful container find to be accepted immediately via the lastSeenId is null short-circuit — bypassing the two-consecutive-polls stabilization intended to guard against stale containers from a previous Aspire run.

Change

• DockerApiClient.cs — Remove lastSeenId = null and isFirstPoll = false from the HttpRequestException catch block. A transient network error carries no information about actual container state; the existing stabilization values must survive across retries.

catch (HttpRequestException ex)
{
    _logger.LogError(ex, "Docker API request failed for {ResourceName}; retrying…", resourceName);

    // Do not reset lastSeenId or isFirstPoll — a transient error gives no information about the
    // container state, so the existing stabilization state must be preserved. Resetting would
    // set lastSeenId to null, causing the next successful find to be accepted immediately via the
    // "appeared after an empty poll" path, which defeats the two-poll confirmation.
}

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.