onto Connectors 2.1.3

We have seen some instabilities in the usage of Connectors with an Azure Kubernetes service. This release addresses these issues.

A bug in our WebDAV implementation did not allow the displayname to be empty in a PROPFIND (browse) response. This is, however, spec valid. We do now support this.