Tests: pytest emits deprecation warning

[elliot-100]

Running tests gives this warning, e.g. from Actions:

Run poetry run pytest
/home/runner/work/Spond/Spond/.venv/lib/python3.9/site-packages/pytest_asyncio/plugin.py:207: PytestDeprecationWarning: The configuration option "asyncio_default_fixture_loop_scope" is unset.
The event loop scope for asynchronous fixtures will default to the fixture caching scope. Future versions of pytest-asyncio will default the loop scope for asynchronous fixtures to function scope. Set the default fixture loop scope explicitly in order to avoid unexpected behavior in the future. Valid fixture loop scopes are: "function", "class", "module", "package", "session"

  warnings.warn(PytestDeprecationWarning(_DEFAULT_FIXTURE_LOOP_SCOPE_UNSET))

Note that this is rather hidden in Actions output - it may be possible to configure the pytest CI step so warnings are highlighted, as the ruff steps already do. (Edit: Pytest publishes a plugin to do this: https://github.com/pytest-dev/pytest-github-actions-annotate-failures?tab=readme-ov-file#warning-annotations)

[Olen]

Fixed by #234 (merged in 48078ed) — added [tool.pytest.ini_options] with asyncio_default_fixture_loop_scope = "function" to pyproject.toml, pinning the fixture loop scope explicitly. The literal deprecation warning text no longer fires in pytest-asyncio 1.x, but pinning it now protects against the future default flip the warning was anticipating.

Closing — the bonus suggestion of using pytest-github-actions-annotate-failures is left as a separate follow-up if desired.