Fix or silence warnings emitted by tests

[dagardner-nv]

Description

• pytest now runs without reporting any warnings on 3.12 (there is a warning 3.11 that pytest is unable to silence), down from 46.
• Update code to avoid several deprecation warnings (mostly Pydantic)
• Silence warnings being emitted by weave that we have no control over (weave triggers PydanticDeprecatedSince20 wandb/weave#4533 & SentryHubDeprecationWarning wandb/weave#3666)
• Add a dependency on langchain-community to aiqtoolkit-test needed for the DeterministicFakeEmbedding class (this is currently a transitory dep of ragas)
• Renamed test classes beginning with Test which were not test classes, to prevent pytest from attempting to run them.
• Avoid mocking the asyncio.run_coroutine_threadsafe method, this ensures that coroutines are awaited.
• Update src/aiq/eval/evaluate.py such that coroutines are only started after passing the if not session_manager.workflow.has_single_output check, and in the event of an exception, cancel any running coroutines in the exception handler.
• Ignore syntax warnings being emitted by qdrant-client used by mem0, remove once the fix for Invalid escape sequence produces SyntaxWarning on run qdrant/qdrant-client#983 is released.

Closes #308

By Submitting this PR I confirm:

• I am familiar with the Contributing Guidelines.
• We require that all contributors "sign-off" on their commits. This certifies that the contribution is your original work, or you have rights to submit it under the same license, or a compatible license.
  • Any contribution which contains commits that are not Signed-Off will not be accepted.
• When the PR is ready for review, new or existing tests cover these changes.
• When the PR is ready for review, the documentation is up to date with these changes.