refactor: separate Direct Editing and legacy Richdocuments APIs

[marinofaggiana]

Summary

This PR generalizes the existing text-specific Direct Editing APIs so they can be used with every editor and creator advertised by the Nextcloud server.

It also clearly separates the core Direct Editing API from the legacy Richdocuments endpoints used by Nextcloud Office/Collabora.

Changes

• Renames NextcloudKit+NCText to NextcloudKit+DirectEditing.
• Replaces the text-specific API names with generic Direct Editing names:
  • getDirectEditingCapabilities
  • openFileForDirectEditing
  • getDirectEditingTemplates
  • createFileForDirectEditing
• Adds editorId and creatorId parameters where required.
• Supports opening files by path and optional file ID.
• Correctly decodes keyed Direct Editing template responses.
• Adds dedicated Direct Editing models:
  • NKDirectEditingEditor
  • NKDirectEditingCreator
  • NKDirectEditingTemplate
• Renames the cached capability properties to:
  • directEditingEditors
  • directEditingCreators
  • directEditingTemplates
• Converts editor and creator dictionaries directly into arrays.
• Renames legacy Richdocuments methods to clarify their purpose:
  • createRichdocumentsEditorURL
  • getRichdocumentsTemplates
  • createRichdocumentsFileFromTemplate
  • createRichdocumentsAssetURL
• Keeps callback-based and async variants of all APIs.

API compatibility

This PR intentionally renames public APIs and model types. Applications using the previous text* or Richdocuments method names must migrate to the new names.

The underlying legacy Richdocuments endpoints remain unchanged.

Related pull requests

• feat: support API in direct editing ios#4249
• feat(direct-editing): integrate with OCP\DirectEditing API richdocuments#5656

Validation

• Integrated and built with the Nextcloud iOS client.
• Nextcloud iOS unit tests passed with this package revision.
• NextcloudKit CI completed successfully.

🤖 AI

• The content of this PR was partly or fully generated using AI.