Wizard: Display error message from unsupported client version reply

[TheOneRing]

23-12-04 07:39:52:456 [ info sync.httplogger ]:	"40113238-73b6-4632-a29a-8a171e3e4180: 
Response: PROPFIND 403 (Error: Error transferring https://demo.owncloud.org/remote.php/webdav/ - server replied: Forbidden,270ms) https://demo.owncloud.org/remote.php/webdav/ 
Header: { Cache-Control: no-store, no-cache, must-revalidate, Content-Length: 220, Content-Security-Policy: default-src 'none';, Content-Type: application/xml; charset=utf-8, Date: Mon, 04 Dec 2023 15:39:52 GMT, Expires: Thu, 19 Nov 1981 08:52:00 GMT, Pragma: no-cache, Referrer-Policy: strict-origin-when-cross-origin, Server: Apache, Set-Cookie: oc_sessionPassphrase=BTWfmYjQ3P%2ByDepHJtbkZqU0hqiaTQiAe61PyvgH2lU%2BQvzTC2sc93ZUH3ZgN17QZAvQ4KSiXfWiLqoo%2FAA9fsjCT6KazAiUBQmNIda63hyHpxvU%2B54ve2aAhg6HUATb; expires=Mon, 04-Dec-2023 15:59:52 GMT; Max-Age=1200; path=/; secure; HttpOnly; SameSite=Lax
oc4qe5jfqnrc=73h8n555khtb9irn682784rdk4; path=/; secure; HttpOnly; SameSite=Lax
cookie_test=test; expires=Mon, 04-Dec-2023 16:39:52 GMT; Max-Age=3600, Strict-Transport-Security: max-age=315360000; preload, X-Content-Type-Options: nosniff, X-Download-Options: noopen, X-Frame-Options: SAMEORIGIN, X-Permitted-Cross-Domain-Policies: none, X-Robots-Tag: none, X-Xss-Protection: 0, } 
Data: [<?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
  <s:exception>Sabre\\DAV\\Exception\\Forbidden</s:exception>
  <s:message>Unsupported client version.</s:message>
  </d:error>
]

Current state:

[michaelstingl]

@TheOneRing Account setup is only half of the story. What about already configured accounts, when the 'minimum.supported.desktop.version' on the server changes? New issue?

[TheOneRing]

@TheOneRing Account setup is only half of the story. What about already configured accounts, when the 'minimum.supported.desktop.version' on the server changes? New issue?

Nothing we can do there as the server does not tell us why we are blocked.

[github-actions]

This issue was marked stale because it has been open for 30 days with no activity. Remove the stale label or comment or this will be closed in 7 days.

[TheOneRing]

#11482 fixes the issue in the way that we now handle the error.
The server only issues the error only after we set everything up and are authenticated...