docs(platform): describe IXP projects service without referencing the CLI

Reword the projects service and facade docstrings to describe the design-time
resources on their own terms (resource-named properties, the design-time
project lifecycle) instead of "the CLI's uip ixp groups". The Python IXP SDK
is independent of the CLI. No behavior change.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: cezara98t

packages/uipath-platform/src/uipath/platform/document_projects/_document_projects_service.py

@@ -2,8 +2,8 @@
 
 :class:`DocumentProjectsService` is the entry point reached via
 ``sdk.document_projects``. It groups the design-time resource services under
-properties that mirror the CLI's command groups (``uip ixp projects``,
-``uip ixp fields``, ...), so callers write ``sdk.document_projects.projects.list()``.
+properties named for each resource (``projects``, ``fields``, ...), so callers
+write ``sdk.document_projects.projects.list()``.
 
 Only the ``projects`` resource is wired today; sibling resources (fields,
 data-types, groups, documents, labellings, deployments) are added as their

packages/uipath-platform/src/uipath/platform/document_projects/_projects_service.py

@@ -1,9 +1,9 @@
 """Design-time projects resource service.
 
-:class:`ProjectsService` covers the project lifecycle exposed by the CLI's
-``uip ixp projects`` group core verbs — list, retrieve, create, update (title),
-delete — over ``du_/api/designtimeapi``. Sub-resources of a project (fields,
-data-types, taxonomy, documents, models, ...) are handled by sibling services.
+:class:`ProjectsService` covers the design-time project lifecycle — list,
+retrieve, create, update (title), delete — over ``du_/api/designtimeapi``.
+Sub-resources of a project (fields, data-types, taxonomy, documents, models,
+...) are handled by sibling services.
 
 It builds on :class:`IxpDesigntimeService`, so writes (create/update/delete) are
 **not** retried while list/retrieve keep the platform retry policy.