[Tests-Only] edit users only when running with oc10 backend

[dpakach]

Description

For acceptance tests when we create users, we send separate requests to set user's email and displayname after the user is created. This is because in oc10 we cannot create user with email, displayname set. but this is possible in ocis
So we can remove sending separate requests when running tests in ocis.
CI in ocis passes https://drone.owncloud.com/owncloud/ocis/1683

Related Issue

• Fixes check if editing a created user in the API tests is needed when testing OCIS #38134

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

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]

Everything that calls usersHaveBeenCreated is passing in $userAttributes['displayName'] - so it is always set, but possibly sometimes to null. I guess that is OK. The request to the "add user" endpoint might go out asking for displayname = null - probable it will be requesting the empty string, or guzzle will ignore that item in the body and not send it at all. On oC10 it does not matter - it ignores a displayname in the "add user" request. On OCIS we might find out what happens if the request explicitly asks for an empty displayname