oCIS sends OCM shares with malformed payload

[glpatcern]

Describe the bug

When an OCM share is created in oCIS, the payload that is sent to the remote end contains the webdav URI as follows:

"protocol": {
    "name": "multi",
    "options": {},
    "webdav": {
      "sharedSecret": "<some-secret>",
      "permissions": [
        "read"
      ],
      "url": "https://ocis-server.domain/dav/ocm/<some-uuid>"
    }
  }

Whereas the OCM spec says that the URI field is named uri, not url. This makes the remote end fail to parse the payload, unless it explicitly looks for url. Therefore, only an oCIS server can receive an oCIS share via OCM.

Steps to reproduce

1. Create an OCM share
2. Observe the payload sent to the other end

Expected behavior

Comply to the OCM spec

Additional context

These tests are being carried in the scope of the EOSC Federation, see the OCM public Matrix channel for further details.

[glpatcern]

#11735 gives details about a related issue