`WSASetup`/`WSACleanup` initialization/de-initialization issues

Currently, lib/net/socket.network_init is invoked to load ws2_32 on Windows via WSASetup, but a subsequent call to WSACleanup is never called.

This is also problematic when calling feature/api/tor_api.tor_main_configuration_setup_control_socket on Windows, and results in failure if the calling application does not first call WSASetup.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information