[Buganizer ID: 548190866] Fix: URL-encode OData $filter parameters for special characters

[pankjsingh-ind]

Description

Fixes OData $filter URL parameter construction in OnePlatformSoarApi by applying urllib.parse.quote() to prevent reserved characters like & in custom list categories and environments from splitting query strings and triggering 400 Bad Request errors.

What problem does this PR solve?

When querying 1Platform endpoints with OData $filter expressions (such as in get_traking_list_records_filtered, get_traking_list_record, and get_cases_by_timestamp_filter), parameters containing reserved URI characters (such as & in environment or category names) caused the web server to split the query string at the ampersand delimiter. This resulted in 400 Client Error: Bad Request or 0 records returned.

How does this PR solve the problem?

Applied urllib.parse.quote() to the $filter query string in OnePlatformSoarApi so that reserved characters (&), spaces, and unicode symbols (e.g. umlauts) are safely percent-encoded (e.g. %26), preserving the full query filter intact across all network requests.

Testing & Verification

• Added dedicated unit tests: test_get_traking_list_records_filtered_url_encoded and test_get_traking_list_record_url_encoded in test_one_platform_soar_api.py.
• Ran full test suite: 16/16 passed.
• Tested live reproduction in Chronicle SOAR UI against environment and category containing & and umlauts (Indevis_Test_&_München).

---

Checklist:

General Checks:

• I have read and followed the project's contributing.md guide.
• My code follows the project's coding style guidelines.
• I have performed a self-review of my own code.
• My changes do not introduce any new warnings.
• My changes pass all existing tests.
• I have added new tests where appropriate to cover my changes.
• I have updated the documentation where necessary.

Open-Source Specific Checks:

• My changes do not introduce any Personally Identifiable Information (PII) or sensitive customer data.
• My changes do not expose any internal-only code examples, configurations, or URLs.
• All code examples, comments, and messages are generic and suitable for a public repository.
• I understand that any internal context or sensitive details related to this work are handled separately in internal systems (Buganizer for Google team members).

For Google Team Members and Reviewers Only:

• I have included the Buganizer ID in the PR title or description (Internal Buganizer ID: 548190866).
• I have ensured that all internal discussions and PII related to this work remain in Buganizer.
• I have tagged the PR with one or more labels that reflect the pull request purpose.

[patilgp-oss]

LGTM!