[tests-only] Adjust tests to better run on PGSQL

[phil-davis]

Description

commits 1,2,3) take the opportunity to let the IDE auto-format the gherkin files. Gets the tables lined-up in scenarios... These are purely cosmetic changes

commit 4) fix PHP doc in TagsContext

commit 5) Make oc:fileid checks more flexible - these scenarios would fail in CI with PGSQL, see #37962 https://drone.owncloud.com/owncloud/core/27379/95/13 - the code was checking for an exactly 10-digit fileid. I made it more flexible to take any length with a-z A-Z 0-9. This should be helpful for other implementations, like different OCIS storages.

commit 6) Do not run Oracle or PostgreSQL as the federated db - installing a 2nd Oracle or PGSQL database in CI is "trouble". Use mariadb in that case. We are not trying to test the particular database on the federated server.

commit 7) Create a separate test suite apiWebdavLocksUnlock - apiWebdavLocks2 had got too many features in it and was taking >1 hour to finish.

How Has This Been Tested?

CI

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Database schema changes (next release will require increase of minor version instead of patch)
• 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:
• Changelog item, see TEMPLATE

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
0 Code Smells

No Coverage information
No Duplication information

[phil-davis]

For the record,
apiWebdavLocks 42 min
apiWebdavLocks2 46 min
apiWebdavLocksUnlock 35 min
looks good