deps!: bump socket2 (to 0.5.3) and MSRV (to 1.63)

[BastiDood]

Motivation

Due to MSRV restrictions, the tokio crate depends on an old version of the socket2 crate that depends on the winapi crate. This is unfortunate because nowadays, we should prefer the officially maintained windows-sys crate for Windows API bindings.

Note that this problem is not only an issue of updating dependencies to the latest version. By keeping the old version of socket2 around, we are forcing consumers of the tokio crate to download and compile two redundant crates in the dependency tree: winapi and windows-sys. With the latter being officially supported, it is about time we prune winapi from the dependency tree.

Solution

This PR bumps socket2 to version 0.5, which is the final piece in the dependency tree that still previously relied on winapi. See the changelog for more details. All references in the documentation and manifest files have been updated accordingly.

Note that this has already been attempted in #5603. However, due to MSRV constraints, the author promptly closed the PR. A few months later, it should now be safe to bump the MSRV to 1.63, which also happens to be the MSRV for socket2. Since 1.63 was released eleven months ago as of writing, we are well beyond the six-month eligibility requirement of the MSRV policy. 🎉

[carllerche]

Thanks for the PR. Before we do something like this, it probably would be worth evaluating if socket2 is worth keeping around. How much are we using it and how hard would it be to implement that functionality ourselves in tokio.

[BastiDood]

... it probably would be worth evaluating if socket2 is worth keeping around. How much are we using it and how hard would it be to implement that functionality ourselves in tokio.

Fair enough. I have not considered this. In all honesty, my original intention was just to bump the dependency so that we could finally prune winapi off of the tree. 😅

But if this PR leads to an exploration that may prune socket2 altogether, then I'm all for that as well! It never hurts to have fewer dependencies. 😃

[KronicDeth]

We'd like the update to socket2 for the watchOS and tvOS support added in socket2 0.5.0 to get support for those architectures in liveview-native/phoenix-channels-client#37. Would the socket2 alternatives support watchOS and tvOS?

[Darksonn]

Closing as duplicate of #5887.

@KronicDeth We are going to be upgrading socket2, so if the new version supports those, then it should work.