Pytest-asyncio

- Adds an optional *loop_scope* keyword argument to *pytest.mark.asyncio*. This argument controls which event loop is used to run the marked async test. [706](https://github.com/pytest-dev/pytest-asyncio/issues/706), [#871](https://github.com/pytest-dev/pytest-asyncio/issues/871)
- Deprecates the optional *scope* keyword argument to *pytest.mark.asyncio* for API consistency with ``pytest_asyncio.fixture``. Users are encouraged to use the *loop_scope* keyword argument, which does exactly the same.
- Raises an error when passing *scope* or *loop_scope* as a positional argument to ``pytest.mark.asyncio``. [812](https://github.com/pytest-dev/pytest-asyncio/issues/812)

- Fixes a bug that caused duplicate markers in async tests [813](https://github.com/pytest-dev/pytest-asyncio/issues/813)

Known issues
As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see [706](https://github.com/pytest-dev/pytest-asyncio/issues/706)). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

- Silence deprecation warnings about unclosed event loops that occurred with certain CPython patch releases [817](https://github.com/pytest-dev/pytest-asyncio/pull/817)

Known issues
As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see [706](https://github.com/pytest-dev/pytest-asyncio/issues/706)). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

- Fix compatibility with pytest 8.2 [800](https://github.com/pytest-dev/pytest-asyncio/pull/800)

Known issues
As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see [706](https://github.com/pytest-dev/pytest-asyncio/issues/706)). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.