Bump mio from 0.8.5 to 0.8.11

[dependabot]

Bumps mio from 0.8.5 to 0.8.11.

Changelog

Sourced from mio's changelog.

0.8.11

• Fix receiving IOCP events after deregistering a Windows named pipe (tokio-rs/mio#1760, backport pr: tokio-rs/mio#1761).

0.8.10

Added

• Solaris support (tokio-rs/mio#1724).

0.8.9

Added

• ESP-IDF framework support (tokio-rs/mio#1692).
• AIX operating system support (tokio-rs/mio#1704).
• Vita support (tokio-rs/mio#1721).
• {UnixListener,UnixStream}:bind_addr (tokio-rs/mio#1630).
• mio_unsupported_force_poll_poll and mio_unsupported_force_waker_pipe unsupported configuration flags to force a specific poll or waker implementation (tokio-rs/mio#1684, tokio-rs/mio#1685, tokio-rs/mio#1692).

Fixed

• The pipe(2) based waker (swapped file descriptors) (tokio-rs/mio#1722).
• The duplicate waker check to work correctly with cloned Registrys. (tokio-rs/mio#1706).

0.8.8

Fixed

• Fix compilation on WASI (tokio-rs/mio#1676).

0.8.7

Added

• Add/fix support for tvOS and watchOS, Mio should now build for tvOS and

... (truncated)

Commits

• 0328bde Release v0.8.11
• 7084498 Fix warnings
• 90d4fe0 named-pipes: fix receiving IOCP events after deregister
• c710a30 Add v0.8.x to the CI
• c29e21c Release v0.8.10
• f6a20da Add Solaris operating system support (#1724)
• e80c3b2 Release v0.8.9
• 862786b Fix importing of IoSourceState
• 4034872 Add support for vita target
• 8eb4010 Fix receiver and sender fd in pipe based waker
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[juntao]

Hello, I am a code review bot on flows.network. Here are my reviews of code commits in this PR.

---

Commit a75b5694807c863786d2b514122c1581b7da0624

Key Changes:

1. The patch updates the mio dependency from version 0.8.5 to 0.8.11 in the Cargo.lock file.
2. The checksum for the mio package has been updated to match version 0.8.11.
3. The windows-sys dependency version has been updated from 0.42.0 to 0.48.0.

Potential Problems:

1. The direct impact of these changes on the project's functionality is uncertain without further context on how mio and windows-sys are being used in the codebase. Additional testing may be required to ensure compatibility with the new versions.
2. Updating dependencies may introduce new bugs or compatibility issues with other parts of the codebase. It is advisable to thoroughly test the application after such upgrades.
3. It's worth checking if there are any specific reasons for pinning the windows-sys dependency to version 0.42.0 previously and if the new version 0.48.0 is compatible with the project requirements.
4. The changes made are only related to dependency updates. No other code changes are included in the patch, which reduces the risk of introducing new issues directly from code modifications but testing is still necessary.

Overall, further validation through testing and potentially reviewing other changes depending on these dependencies in the project's codebase is recommended to ensure the stability and functionality of the application after these updates.