[Bug]: provisioning_api current user display name field #36539

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• Nextcloud Server is running on 64bit capable CPU, PHP and OS.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

3e6c40e#diff-388d86396b3a70ff465e035b0db5d78bce90716631ab322d00425fbb317042ebR214 has a hack that sets the display-name and removes the displayname field. It seems like this was done to match an older API.
Ideally I'd like to drop this in order to make the API output the same regardless of requesting the current user or any other user, we should probably just set both fields for all APIs to make it easier for clients, because otherwise they have to switch between these different fields.

Steps to reproduce

/

Expected behavior

Only the same one field set for all APIs or both fields set for all APIs.

Installation method

None

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

No response

List of activated Apps

/

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response