Check marker arguments

[Cito]

This PR implements error checking for the arguments of mark.asyncio.

An ValueError with a helpful message is raised when unexpected arguments are passed.

This should fix issue #812.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 91.50%. Comparing base (a8b3d18) to head (db7a1c6).
Report is 2 commits behind head on main.

Files	Patch %	Lines
pytest_asyncio/plugin.py	0.00%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #886      +/-   ##
==========================================
- Coverage   91.86%   91.50%   -0.37%     
==========================================
  Files           2        2              
  Lines         504      506       +2     
  Branches       99      100       +1     
==========================================
  Hits          463      463              
- Misses         24       25       +1     
- Partials       17       18       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[seifertm]

Thanks for the patch!

I rebased the code to main and adjusted the tests to use the new loop_scope kwargs rather than the deprecated scope kwarg to @pytest.mark.asyncio.

I also added a changelog entry.

[MeggyCal]

As this error is thrown at every unrecognized keyword argument, could it be improved to something more generic, please?

[seifertm]

@MeggyCal What problem are you encountering and what improvement do you suggest to solve it?

[MeggyCal]

Hi, I've been debugging redis/redis-py#3339 lately. I find mark.asyncio accepts only a keyword argument 'scope' cryptic at this point, it would be better to throw mark.asyncio: Unrecognized keyword argument: %s or mark.asyncio does not accept positional arguments. Did you mean to use 'scope'? depending on the context.