[FEATURE REQUEST] [oCIS] Respect Capability "privateLinks": false

[michaelstingl]

Is your feature request related to a problem? Please describe.

oCIS doesn't have the oC10-style private links. It's also announced as false in the capabilities:

% cat ocis.capabilities | jq .ocs.data.capabilities.files
{
  "privateLinks": false,
  "bigfilechunking": false,
  "undelete": true,
  "versioning": true,
  "favorites": false,
  "blacklisted_files": [],
  "tus_support": {
    "version": "1.0.0",
    "resumable": "1.0.0",
    "extension": "creation,creation-with-upload",
    "max_chunk_size": 100000000,
    "http_method_override": ""
  },
  "archivers": [
    {
      "enabled": true,
      "version": "2.0.0",
      "formats": [
        "tar",
        "zip"
      ],
      "archiver_url": "/archiver",
      "max_num_files": "10000",
      "max_size": "1073741824"
    }
  ],
  "app_providers": [
    {
      "enabled": true,
      "version": "1.0.0",
      "apps_url": "/app/list",
      "open_url": "/app/open",
      "new_url": "/app/new"
    }
  ]
}

Describe the solution you'd like

iOS app should respect the capability, and hide the private link entries on all screens.

Additional context

Desktop issues:

• [oCIS] Respect Capability "privateLinks": false client#9573
• Desktop client should respect "privateLinks":false from capabilities client#8998

Android issue:

• [FEATURE REQUEST] [oCIS] Respect Capability "privateLinks": false android#3732

TASKS

• Research (if needed)
• Create branch feature/feature_name
• Development tasks
  • Implement whatever
  • ...
• Code review and apply changes requested
• Design test plan
• QA
• Merge branch feature/feature_name into master

PR

• App
• Library (if needed)