chore(deps): bump uipath and uipath-platform, fix test type errors

uipath-platform 0.2.32 -> 0.2.33 and uipath 2.14.24 -> 2.14.25, since both
packages carry source changes here and the versions on main are already on
PyPI. uipath's lower bound on uipath-platform moves to >=0.2.33 so a
standalone install cannot resolve a release without the binding metadata.

The overwrite fixtures in the binding tests were built with field aliases,
which the pydantic mypy plugin rejects. They now go through
ResourceOverwriteParser, the same path the runtime uses on the server's
response, so the test also exercises production construction.

Author: tudormatei1

packages/uipath-platform/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "uipath-platform"
-version = "0.2.32"
+version = "0.2.33"
 description = "HTTP client library for programmatic access to UiPath Platform"
 readme = { file = "README.md", content-type = "text/markdown" }
 requires-python = ">=3.11"

packages/uipath/pyproject.toml

@@ -1,13 +1,13 @@
 [project]
 name = "uipath"
-version = "2.14.24"
+version = "2.14.25"
 description = "Python SDK and CLI for UiPath Platform, enabling programmatic interaction with automation services, process management, and deployment tools."
 readme = { file = "README.md", content-type = "text/markdown" }
 requires-python = ">=3.11"
 dependencies = [
   "uipath-core>=0.5.30, <0.6.0",
   "uipath-runtime>=0.13.5, <0.14.0",
-  "uipath-platform>=0.2.31, <0.3.0",
+  "uipath-platform>=0.2.33, <0.3.0",
   "uipath-ipc>=2.5.1, <2.6.0",
   "click>=8.3.3, <9.0.0",
   "httpx>=0.28.1",

packages/uipath/tests/cli/test_cli_bindings.py

@@ -2,6 +2,7 @@
 import os
 from pathlib import Path
 from types import SimpleNamespace
+from typing import Any
 from unittest.mock import AsyncMock, MagicMock
 
 import pytest
@@ -17,8 +18,7 @@
 from uipath._cli._push._resource_actions import CreateVirtual
 from uipath._cli.models.runtime_schema import Bindings
 from uipath.platform.common._bindings import (
-    ConnectionResourceOverwrite,
-    GenericResourceOverwrite,
+    ResourceOverwriteParser,
     _resource_overwrites,
     resource_override,
 )
@@ -454,20 +454,16 @@ def test_override_applies_to_the_generated_key(self, source: str) -> None:
 
         probe = _make_probe(spec)
         overwrite_key = f"{ref.resource_type}.{binding.key}"
-        if ref.resource_type == "connection":
-            overwrite = ConnectionResourceOverwrite(
-                resource_type="connection",
-                connectionId="NEW_ID",
-                folderKey="NEW_FOLDER",
-            )
-        else:
-            overwrite = GenericResourceOverwrite(
-                resource_type=ref.resource_type,
-                name="NEW_NAME",
-                folderPath="NEW_FOLDER",
-            )
+        # Built through the same parser the runtime uses on the server's
+        # response, so the test exercises the production construction path.
+        payload: dict[str, Any] = (
+            {"connectionId": "NEW_ID", "folderKey": "NEW_FOLDER"}
+            if ref.resource_type == "connection"
+            else {"name": "NEW_NAME", "folderPath": "NEW_FOLDER"}
+        )
+        overwrite = ResourceOverwriteParser.parse(overwrite_key, payload)
 
-        call_args = {spec.name_param: ref.name}
+        call_args: dict[str, Any] = {spec.name_param: ref.name}
         if spec.folder_param:
             call_args[spec.folder_param] = ref.folder_path
 
@@ -620,7 +616,7 @@ def _make_probe(spec):
     if spec.folder_param:
         params.append(f"{spec.folder_param}=None")
     folder_expr = spec.folder_param if spec.folder_param else "None"
-    namespace: dict = {}
+    namespace: dict[str, Any] = {}
     exec(
         f"def probe({', '.join(params)}):\n"
         f"    return ({spec.name_param}, {folder_expr})\n",