Python: Fixes to Cosmos DB NoSQL query syntax generation.

[davidatorres]

Motivation and Context

Review information:

1. Why is this change required?

There were several SQL query syntax generation issue for both text_search() and vectorized_search() methods

2. What problem does it solve?

a) In _build_where_clauses_from_filter() the WHERE clause creation did not quote string values and did not properly handle list[] data model attribures,
b) for _build_vector_query() method the WHERE clause was placed after the ORDER BY clause causing query syntax errors,
c) for _build_search_text_query() method the data_model_definition items were not being interrogated, thus added CONTAINS() in the WHERE clause.

3. What scenario does it contribute to?

The ability to use Azure Cosmos DB NoSQL for text_search() and vectorized_search().

4. Issue resolution:
   Python: Bug: AzureCosmosDBNoSQLCollection text_search() and vectorized_search() produce incorrect results due to malformed query strings. #10368

Description

The errors noted in the Issue and the bug fixes noted above correct the SQL query syntax generation for the text_search() and vectorized_search() methods and now produce accurate results for performing both types of queries with and without filters (aka WHERE clause).

Contribution Checklist

• ✅ The code builds clean without any errors or warnings
• ✅ The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
• ✅ All unit tests pass, and I have added new tests where possible
• 🙏 I didn't break anyone 😄

[markwallace-microsoft]

Python Test Coverage Report •

File	Stmts	Miss	Cover	Missing
semantic_kernel/connectors/memory/azure_cosmos_db
azure_cosmos_db_no_sql_collection.py	171	67	61%	98–99, 140–147, 158–172, 178–186, 192–196, 219–243, 247, 251, 275, 303–304, 308–313
TOTAL	17838	2015	89%

Python Unit Test Overview

Tests	Skipped	Failures	Errors	Time
3135	4 💤	0 ❌	0 🔥	1m 26s ⏱️

[moonbox3]

Hi @davidatorres, thanks for the PR! Have you installed the pre-commit locally? There's a rough error that needs to be fixed on your machine before pushing upstream. If you haven't installed the pre-commit, you can do so by running:

uv run pre-commit install -c python/.pre-commit-config.yaml

Now, when you running git commit -m "Your message" it will run the required steps, and alert you that there is a ruff formatting fix required.

[moonbox3]

Are there any further unit tests we need to exercise the new code?

[davidatorres]

No new tests needed. Updates correct the generation of the SQL queries to ensure that they are populated and formatted correctly.