chore(deps): update dependency pytest-randomly to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
pytest-randomly (changelog)	^3.7.0 → ^4.0.0

---

Release Notes

pytest-dev/pytest-randomly (pytest-randomly)

v4.1.0

Compare Source

• Fix a crash with Faker installed when explicitly enabling and disabling the plugin (via -p randomly -p no:randomly).

  Thanks to mojosan77 for the report in Issue #&#8203;718 <https://github.com/pytest-dev/pytest-randomly/issues/718>__.

• Drop Python 3.9 support.

v4.0.1

Compare Source

• Remove the random state caching, which would grow without bound, leaking memory in long test runs.
  The caching was added to slightly speed up re-using the same (final) seed, but since the final seed is now different for each test, it has no effect.

  PR #&#8203;690 <https://github.com/pytest-dev/pytest-randomly/issues/687>__.

• Modify Numpy seed restriction, replacing hashing with a modulo operation.
  The extra work to hash is unnecessary now that we generate a final seed per test with CRC32.
  This change saves ~500ns per test when Numpy is installed.

  PR #&#8203;691 <https://github.com/pytest-dev/pytest-randomly/issues/691>__.

v4.0.0

Compare Source

• Support Python 3.14.

• Use a different random seed per test, based on the test ID.

  This change should mean that tests exercise more random data values in a given run, and that any randomly-generated identifiers have a lower chance of collision when stored in a shared resource like a database.

  PR #&#8203;687 <https://github.com/pytest-dev/pytest-randomly/issues/687>.
  Thanks to Bryce Drennan for the suggestion in Issue #&#8203;600 <https://github.com/pytest-dev/pytest-randomly/issues/600> and initial implementation in PR #&#8203;617 <https://github.com/pytest-dev/pytest-randomly/pull/617>__.

• Move from MD5 to CRC32 for hashing test IDs, as it’s 5x faster and we don’t need cryptographic security.

  Issue #&#8203;686 <https://github.com/pytest-dev/pytest-randomly/issues/686>__.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.

[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: poetry.lock

Updating dependencies
Resolving dependencies...


The current project's supported Python range (>=3.9,<3.12) is not compatible with some of the required packages Python requirement:
  - typer requires Python >=3.10, so it will not be satisfied for Python >=3.9,<3.10

Because micropy-cli depends on typer[all] (0.26.7) which requires Python >=3.10, version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For typer, a possible solution would be to set the `python` property to ">=3.10,<3.12"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers