fix: hardcode config for spaces which was not allowed to change

[kulmann]

Description

Stumbled over two environment variables for which even the description states that they are not allowed to be changed. This PR has two positive results:

• reduced the risk to misconfigure ocis
• will allow the web team to remove capability checks in web, because ocis is the only allowed backend. Since other clients are checking those capabilities, we can't remove the capabilities entirely.

I consider this to be a bugfix because the description of the env vars hints towards broken ocis if those config variables are set to other values than those which I now hardcoded.

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 ticket raised:

[sonarcloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[kulmann]

cc @JammingBen @janackermann if this gets merged we can remove a lot of ifs from the web master