Some psycopg async tests don't run

[xrmx]

Describe your environment

Steps to reproduce

tox -e py310-test-instrumentation-psycopg

What is the expected behavior?

No warnings

What is the actual behavior?

instrumentation/opentelemetry-instrumentation-psycopg/tests/test_psycopg_integration.py::TestPostgresqlIntegration::test_instrumentor_with_async_connection_class
  /usr/lib/python3.10/unittest/case.py:549: RuntimeWarning: coroutine 'TestPostgresqlIntegration.test_instrumentor_with_async_connection_class' was never awaited
    method()
  Enable tracemalloc to get traceback where the object was allocated.
  See https://docs.pytest.org/en/stable/how-to/capture-warnings.html#resource-warnings for more info.

instrumentation/opentelemetry-instrumentation-psycopg/tests/test_psycopg_integration.py::TestPostgresqlIntegration::test_not_recording_async
  /usr/lib/python3.10/unittest/case.py:549: RuntimeWarning: coroutine 'TestPostgresqlIntegration.test_not_recording_async' was never awaited
    method()
  Enable tracemalloc to get traceback where the object was allocated.
  See https://docs.pytest.org/en/stable/how-to/capture-warnings.html#resource-warnings for more info.

instrumentation/opentelemetry-instrumentation-psycopg/tests/test_psycopg_integration.py::TestPostgresqlIntegration::test_span_name_async
  /usr/lib/python3.10/unittest/case.py:549: RuntimeWarning: coroutine 'TestPostgresqlIntegration.test_span_name_async' was never awaited
    method()
  Enable tracemalloc to get traceback where the object was allocated.
  See https://docs.pytest.org/en/stable/how-to/capture-warnings.html#resource-warnings for more info.

instrumentation/opentelemetry-instrumentation-psycopg/tests/test_psycopg_integration.py::TestPostgresqlIntegration::test_wrap_async_connection_class_with_cursor
  /usr/lib/python3.10/unittest/case.py:549: RuntimeWarning: coroutine 'TestPostgresqlIntegration.test_wrap_async_connection_class_with_cursor' was never awaited
    method()
  Enable tracemalloc to get traceback where the object was allocated.
  See https://docs.pytest.org/en/stable/how-to/capture-warnings.html#resource-warnings for more info.

Additional context

This is not psycopg specific, asyncpg tests had the same issue in running async tests. So once a solution is found we should probably apply it in more places.

[aabmass]

I also noticed that pytest-asyncio is sometimes not installed which is supposed to handle these https://github.com/search?q=repo%3Aopen-telemetry%2Fopentelemetry-python-contrib%20pytest.mark.asyncio&type=code

Maybe we can move all of those to use IsolatedAsyncioTestCase as well

[xrmx]

@aabmass Done, removed pytest-asyncio markers and dependencies from grpc that didn't need them. Double checked the very same number of tests is run.