MPT-18065 MPT API client - Fix backward incompatible issues related to RQL: Support of property comparison

[jentyk]

Closes MPT-18065

• Upgrade mpt-api-client dependency from 5.1.* to 5.2.* in pyproject.toml to enable RQL property comparison support
• No other functional or public API changes

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 79426e2 and 35187ba.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• pyproject.toml

🚧 Files skipped from review as they are similar to previous changes (1)

• pyproject.toml

---

📝 Walkthrough

Walkthrough

Update mpt-api-client dependency from 5.1.* to 5.2.* in pyproject.toml. Minor formatting changes to license, coverage, ruff lint, and manifest entries (whitespace/line-wrapping). No semantic or public API changes.

Changes

Cohort / File(s)	Summary
Dependency and Configuration Updates pyproject.toml	Bumps mpt-api-client from 5.1.* to 5.2.*. Adjusts formatting/whitespace for license, tool.coverage.report, tool.ruff lint settings, and manifest array layout. No functional changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Jira Issue Key In Title	✅ Passed	The PR title contains exactly one Jira issue key in the correct format: MPT-18065.
Test Coverage Required	✅ Passed	No Python code files were modified; only dependency version in pyproject.toml was updated, so no test changes are required.
Single Commit Required	✅ Passed	The PR contains exactly one commit updating mpt-api-client dependency from 5.1.* to 5.2.* in pyproject.toml, satisfying the single commit requirement.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[svazquezco]

please, keep the changes limited to what you're modifing, and don't remove the revision from uv.lock

You can use the make command

make uv-add pkg=mpt-api-client==5.2.0

Then, you can go to the pyproject.toml and change the current 5.2.0 version to 5.2.*

[jentyk]

please, keep the changes limited to what you're modifing, and don't remove the revision from uv.lock

You can use the make command

make uv-add pkg=mpt-api-client==5.2.0

Then, you can go to the pyproject.toml and change the current 5.2.0 version to 5.2.*

@svazquezco
uv documentation says clearly here what needs to be done to upgrade a package and this is what I did.
I do not use make commands you created for uv, as in my opinion in many cases they are redundant, they just create confusion by wrapping one command into another one not adding any value.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud