Update Rust crate sysinfo to 0.35.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
sysinfo	dependencies	minor	0.34.0 -> 0.35.0

---

Release Notes

GuillaumeGomez/sysinfo (sysinfo)

v0.35.0

• Update MSRV to 1.75.
• Add System::open_files_limit.
• Add Process::kill_and_wait and Process::kill_with_and_wait methods.
• Process::open_files* methods return usize.
• set_open_files_limit argument type is usize.
• Code example was improved.
• macOS: Fix M4 CPU frequency calculation.
• Linux: Correctly handle when new CPUs are added.
• Linux: Ignore autofs disks.
• Linux (raspberry pi): Retrieve more thermal zones.
• Android: Update documentation to mention that newer Android version don't allow to retrieve CPU information.
• Windows: Improve Process::wait code.
• Windows: Fix Groups::refresh.

v0.34.2

• FreeBSD: Fix segfault when refreshing processes.

v0.34.1

• macOS: Remove forgotten debug print.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[sourcery-ai]

Reviewer's Guide

This pull request updates the sysinfo Rust crate dependency from version 0.34.0 to 0.35.0 across multiple Cargo.toml files.

File-Level Changes

Change	Details	Files
Updated sysinfo dependency version.	Modified the sysinfo dependency line in [dependencies] section to specify version 0.35.0.	memN0ps/arsenal-rs/rdi-rs/inject/Cargo.toml memN0ps/arsenal-rs/shellcode_runner_classic-rs/Cargo.toml memN0ps/eagle-rs/client/Cargo.toml memN0ps/mimiRust/Cargo.toml memN0ps/mmapper-rs/loader/Cargo.toml memN0ps/mordor-rs/freshycalls_syswhispers/Cargo.toml memN0ps/mordor-rs/hells_halos_tartarus_gate/Cargo.toml memN0ps/pemadness-rs/pemadness/Cargo.toml memN0ps/srdi-rs/generate_shellcode/Cargo.toml memN0ps/srdi-rs/inject/Cargo.toml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.