[stable30] Keep layout on sync errors

[backportbot]

Backport of #6903

Warning, This backport's changes differ from the original and might be incomplete ⚠️

Todo

• Review and resolve any conflicts
• Remove all the empty commits
• Amend HEAD commit to remove the line stating to skip CI
• combine with [stable30] fix(ui): style conflict resolution buttons #6971

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 53.60%. Comparing base (21d2bdc) to head (bc112bb).
Report is 82 commits behind head on stable30.

Additional details and impacted files

@@            Coverage Diff            @@
##           stable30    #6943   +/-   ##
=========================================
  Coverage     53.60%   53.60%           
=========================================
  Files           116      116           
  Lines          2582     2582           
  Branches        526      524    -2     
=========================================
  Hits           1384     1384           
  Misses         1070     1070           
  Partials        128      128           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[max-nextcloud]

This includes a css change that breaks the conflict screen and is fixed by #6964 - so we should backport them in the same release.

[max-nextcloud]

Closing this as the fix for flaky connections in #7097 also introduced a delay for the error message.
This way the error message will only shift the editor around when it's readonly already. So not important enough to warrant a backport.