fix(adms): align API surface with live ADMS wire format

[ShiwaliKusum]

Disclaimer: Do not include SAP-internal or customer-specific information in this PR (e.g. internal system URLs, customer names, tenant IDs, or confidential configurations). This is a public repository.

Description

Aligns the ADMS Python SDK API surface with the live ADM service wire format. Several entity paths, key structures, and method signatures were incorrect — they compiled but failed at runtime (HTTP 400/404) against the real service.

Configuration API fixes:

• DocumentTypeBusinessObjectTypeMap uses a composite key (DocumentTypeID + BusinessObjectNodeTypeUniqueID), not a single UUID. get_type_mapping, delete_type_mapping, and mark_default updated accordingly.
• FileExtensionPolicy entity set renamed from FileExtensionPolicy to DocumentTypeFileExtensionPolicy (matches $metadata). Model fields corrected to DocumentTypeID + FileExtension composite key; get_file_extension_policy(uuid) removed as no such UUID key exists in ADM.
• CreateDocumentTypeBoTypeMapInput wire field names corrected from DocumentTypeId/BusinessObjectNodeTypeUniqueId to DocumentTypeID/BusinessObjectNodeTypeUniqueID.
• MimeTypePolicy removed from public __init__ exports (no longer referenced by any public model).

Document API fixes:

• update() (sync + async): removed the implicit follow-up GET — the UpdateDocument action returns the partial response directly from ADM; callers who need the full document should call get() explicitly.
• get_download_url() (sync + async): doc_content_version_id is now optional (None → DownloadDocument() for latest version), matching the OData Core.OptionalParameter annotation.

Job API fixes:

• StartJob and JobStatus called without namespace prefix (unbound action/function imports do not use namespace prefix per OData spec).

Related Issue

Closes #https://jira.tools.sap/browse/RBSADMS-47

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Code refactoring
• Dependency update

How to Test

1. Configure credentials: set -a && source .env.adms && set +a
2. Run unit tests: uv run pytest tests/adms/unit/ -v
3. Run integration tests against a live ADM instance: uv run pytest tests/adms/integration/ -v
4. Verify cfl, cmg, cmd, cgf, jz, js commands work against the live tenant using scripts/adms_cli.py

Checklist

• I have read the Contributing Guidelines
• I have verified that my changes solve the issue
• I have added/updated automated tests to cover my changes
• All tests pass locally
• I have verified that my code follows the Code Guidelines
• I have updated documentation (if applicable)
• I have added type hints for all public APIs
• My code does not contain sensitive information (credentials, tokens, etc.)
• I have followed Conventional Commits for commit messages

Breaking Changes

get_type_mapping and delete_type_mapping now require two arguments (document_type_id, business_object_node_type_unique_id) instead of one. However, the previous single-argument version accepted a DocumentTypeBOTypeMapID that the ADM service never supported — every call returned HTTP 400. Since the old signature was non-functional, this is treated as a bug fix rather than a breaking API change.

get_file_extension_policy(uuid) is removed. The ADM entity has no UUID primary key; policies are identified by (DocumentTypeID, FileExtension). The old method would have always returned HTTP 404.

update() no longer performs an implicit GET after updating a document. The return value is now the partial action response from ADM (only changed fields). Callers requiring the full document after an update should call documents.get() explicitly.

Additional Notes

All fixes were validated against a live ADM playground tenant. The scripts/adms_cli.py interactive CLI (kept locally, not included in this PR) was used for end-to-end verification of each endpoint.

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ adwitiyasushant
❌ I766515

---

I766515 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[NicoleMGomes]

PR description is not following our template. Only raise PRs to us once it's complete.