* feat: add 'condition' parameter to flaky marker

This introduces a condition parameter to the `@pytest.mark.flaky`
decorator, allowing for more granular control over when a test is rerun.

The condition can be a callable or a string.

If it's a callable, it will be passed the exception object from the
failed test. The test will be rerun only if the callable returns True.

If it's a string, it will be evaluated with the following objects in
its global context: os, sys, platform, config, and error (the
exception instance). The test will be rerun only if the string
evaluates to True.

Exceptions raised by a condition callable are now caught and logged as a
warning, preventing the test suite from crashing.

Issue #230


---------

Co-authored-by: Michael Howitz <m.howitz@minddistrict.com>

See #260 and #290.

Co-authored-by: Michael Howitz <icemac@gmx.net>

Co-authored-by: Michael Howitz <icemac@gmx.net>

* Revert "Allow to pass a callable condition to the `flaky` marker (#299)"

This reverts commit bd8cb4d.

Co-authored-by: Michael Howitz <icemac@gmx.net>

* Drop support for Python 3.9.

Bumps the actions group with 1 update: [actions/setup-python](https://github.com/actions/setup-python).


Updates `actions/setup-python` from 5 to 6
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](actions/setup-python@v5...v6)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Add a `--force-reruns` to override rerun count globally

Add a new `--force-reruns` command-line option that can be used to
override the rerun count globally, irrespectively of individual test
markers.

Fixes #306.

Signed-off-by: Michał Górny <mgorny@gentoo.org>

---------

Signed-off-by: Michał Górny <mgorny@gentoo.org>
Co-authored-by: Michael Howitz <icemac@gmx.net>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

…mark_test_pending` (#309)

* Fix NotImplementedError crash when using xdist schedulers without mark_test_pending

Handle gracefully when pytest-xdist schedulers (like LoadScopeScheduling)
don't implement mark_test_pending by catching NotImplementedError and
failing the test with a clear message instead of crashing the test run.

When a test crashes and cannot be rescheduled:
- Set report outcome to "failed" with informative error message
- Explain which scheduler lacks rescheduling support
- Show remaining rerun count that couldn't be used
- Continue test execution instead of internal crash

Fixes #247


---------

Co-authored-by: Michael Howitz <icemac@gmx.net>