Correctly determine AnyIO support kwargs for run_sync

[Stealthii]

#202 introduces an issue on py38 and py39 with an earlier version of importlib.metadata not detecting versions in certain virtual environments. It also uses string comparisons:

Traceback (most recent call last):
  File "example/lib64/python3.8/site-packages/asyncer/__init__.py", line 3, in <module>
    from ._main import PendingValueException as PendingValueException
  File "example/lib64/python3.8/site-packages/asyncer/_main.py", line 17, in <module>
    from asyncer._compat import run_sync
  File "example/lib64/python3.8/site-packages/asyncer/_compat.py", line 16, in <module>
    if ANYIO_VERSION >= "4.1.0":
TypeError: '>=' not supported between instances of 'NoneType' and 'str'

This PR addresses the issue by using inspect to determine anyio's supported kwargs for the run_sync method.

[Stealthii]

This bug affects v0.0.8 (the latest version) only.

The PR also contains as prior solution to correctly detect AnyIO package version using importlib-metadata and numeric comparison for Python < 3.10, however this was ultimately replaced with the kwargs check.

We should avoid relying on importlib.metadata outside of build environments as it relies heavily on discoverable dist-info or egg-info metadata, which may not be available in non-virtualenv setups (such as system-level packages).

[Stealthii]

@tiangolo I would recommend merging and releasing this in the next version before dropping Python 3.8 support.

[Stealthii]

This still affects non-venv environments. This should be merged and released, as any packages using this that are installed as part of a system install (or flat package) have to explicitly block v0.0.8 from dependency mapping.

[auvipy]

can you check why the check level is failing?