Fix collaboration service name

[micbar]

Description

We decided to

• Move the collaboration service inside the single process
• Add a proxy rule (feat: make it possible to start the collaboration service in the single process #1569)
• Use new defaults for the service name to make it work out of the box

We are assuming that you only need one weboffice application.

In rare cases, you can start a second collaboration service standalone and give it a different service name by setting COLLABORATION_SERVICE_NAME=collaboration-custom or something else.

Related Issue

• Needed by https://github.com/opencloud-eu/opencloud-charts/issues/84

Motivation and Context

How Has This Been Tested?

• test environment:
• test case 1:
• test case 2:
• ...

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation added

[micbar]

@ScharfViktor My last commit sets a service name because that is now needed. No changes when running a single WebOffice.