Allow configuring separate public and internal collabora urls

[juliusknorr]

While we have a hidden app config value for the public wopi url, it would be more straight forward to have this configurable in the UI. This would also allow us to remove some flaky logic to dynamically set the public url.

• Collabora URL (used by Nextcloud server)
• Public Collabora URL (used by the users browser)
  • Fallback to default (internal) Collabora URL if not set (for most cases)
• Internal Nextcloud URL (can be used to set a different callback url for Collabora to send WOPI requests to Nextcloud)
  • Fallback to current request server URL (for most cases)

This would allow direct communication between Nextcloud/Collabora which can be beneficial to avoid always going through reverse proxies.

[cyfrax]

Very good point, I cannot run collabora in my environment as all virtual servers run behind one apache reverse proxy and internal URLs are different to external URLs. I cannot access the external URL from internal servers. However, the collabora app seems to insist on accessing the collabora code server via external urls.

[dhrenek]

Great request. For safety reasons alone it is strange that an internal office host can not be used when accessing your cloud instance externally. Keep as much data inside the local network.