chore(deps): update rust crate getrandom to 0.3.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
getrandom	workspace.dependencies	minor	0.2.14 -> 0.3.0

---

Release Notes

rust-random/getrandom (getrandom)

v0.3.1

Compare Source

Fixed

• Build error on Android #​588

v0.3.0

Compare Source

Breaking Changes

Changed

• Bump MSRV to 1.63 #​542
• Rename getrandom and getrandom_uninit functions to fill and fill_uninit respectively #​532

Removed

• wasm32-wasi target support (use wasm32-wasip1 or wasm32-wasip2 instead) #​499
• linux_disable_fallback, rdrand, js, test-in-browser, and custom crate features
  in favor of configuration flags #​504
• register_custom_getrandom! macro #​504
• Implementation of From<NonZeroU32> for Error and Error::code method #​507
• Internet Explorer 11 support #​554
• Target-specific assocciated Error constants #​562

Changed

• Use ProcessPrng on Windows 10 and up, and use RtlGenRandom on older Windows versions #​415
• Do not use locale-specific strerror_r for retrieving error code descriptions #​440
• Avoid assuming usize is the native word size in the rdrand backend #​442
• Do not read from errno when libc did not indicate error on Solaris #​448
• Switch from libpthread's mutex to futex on Linux and to nanosleep-based wait loop
  on other targets in the use_file backend #​490
• Do not retry on EAGAIN while polling /dev/random on Linux #​522
• Remove separate codepath for Node.js in the wasm_js backend
  (bumps minimum supported Node.js version to v19) #​557
• Use js_namespace in the wasm_js backend #​559

Added

• wasm32-wasip1 and wasm32-wasip2 support #​499
• getrandom_backend configuration flag for selection of opt-in backends #​504
• Error::new_custom method #​507
• rndr opt-in backend #​512
• Automatic MemorySanitizer support #​521 #​571
• u32 and u64 functions for generating random values of the respective type #​544
• wasm32v1-none support in the wasm_js backend #​560
• wasm_js crate feature which allows users to enable the wasm_js opt-in backend #​574

Fixed

• NetBSD fallback code based on KERN_ARND #​555

---

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --workspace
    Updating crates.io index
error: failed to select a version for `getrandom`.
    ... required by package `vortex-array v0.24.0 (/tmp/renovate/repos/github/spiraldb/vortex/vortex-array)`
    ... which satisfies path dependency `vortex-array` (locked to 0.24.0) of package `vortex v0.24.0 (/tmp/renovate/repos/github/spiraldb/vortex/vortex)`
    ... which satisfies path dependency `vortex` (locked to 0.24.0) of package `bench-vortex v0.24.0 (/tmp/renovate/repos/github/spiraldb/vortex/bench-vortex)`
versions that meet the requirements `^0.3.0` (locked to 0.3.1) are: 0.3.1

the package `vortex-array` depends on `getrandom`, with features: `js` but `getrandom` does not have these features.


failed to select a version for `getrandom` which could resolve this conflict

[robert3005]

This is cursed, they renamed a feature from "js" to "wasm_js". This bump has to wait for our dependents to upgrade getrandom

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[robert3005]

We pull in getrandom 0.2 via aHash, reqwest (hyper -> rustls -> ring), uuid and flume. Datafusion bump would cover aHash and uuid. We still need to chase down ring briansmith/ring#2342 and nanorand Absolucy/nanorand-rs#54

[robert3005]

Story continues apache/arrow-rs#7125, people struggle upgrading