[fix] download: apply socket-timeout before extends resolution
A software-release build could hang indefinitely when a remote extends = URL stalled mid-connection (TLS handshake done, no data ever sent or received, no RST/FIN delivered, as happens behind QEMU slirp networking). socket.setdefaulttimeout() from the socket-timeout option was only applied in Buildout._setup_socket_timeout(), called well after remote extends had already been resolved, so it offered no protection for that path.
Download now has its own per-socket default timeout (60s), read from the same socket-timeout option, and passed explicitly to urlopen(). This covers every Download() call site, including the extends download, without relying on socket.setdefaulttimeout() timing. socket.setdefaulttimeout() is now also applied early, before extends resolution, for in-process code that consults socket.getdefaulttimeout() directly; this is a no-op unless socket-timeout is explicitly configured.
Add TestSocketTimeout, which uses a listener that accepts a connection and never answers, covering both a plain download and a remote extends =.