Fix server freeze on client absence.

The server has no concept of clients disconnecting due to networking faults or purposely pulling their internet connection. The current behavior is the server freezes forever waiting for the missing clients to respond until the game timeouts.

This is incredibly frustrating for free-for-all and to an extent, larger team games. More often than not players wish to continue. This fixes the bug by recognizing that clients aren't communicating and eventually drops them so the game can continue.

First the server responds to say it's still alive and waiting, then after a while it shows who isn't responding. Finally after 2 minutes it drops the players. I recommend at least 1.5 minutes before dropping players as often a router can be restarted within a minute and in the original games often found you'd missed the 60 second deadline only by a few seconds.

This is an important fix as the majority of games going down on hetzner, etc. are because of this.
You can simplify this to avoid the explicit list:
```csharp
var notResponding = timeouts.Where(c => (Game.RunTime - c.LastResponse) > BlameInterval)
	.Select(server.GetClient(c).Name);
```
This also addresses two style nits: we generally use `c` when enumerating over clients, and the resulting collection should be named to match what it holds.