On the permission page cm:authorityName is used instead of cm:authorityDisplayName

[AlgoJerViA]

Describe the bug
On the permission page cm:authorityName is used instead of cm:authorityDisplayName, this can create a lot of confusion since the names do not always match.
That is we see as an example GROUP_site_swsdp_SiteManager instead of site_swsdp_SiteManager.

Environment

• ACA version: 4.4.1 (also all other versions I believe, were first noticed in 4.1.0)
• ACS version: 6.7.1

To Reproduce
Steps to reproduce the behavior:
Open any node that has directly set permissions and observe the names.

Expected behavior
I expect to see the cm:authorityDisplayName in the front end and not cm:authorityName as we do in the old Share environment.

Additional context
At the core, the API is to blame, the permission page does the following call:
http://localhost:4200/alfresco/api/-default-/public/alfresco/versions/1/nodes/b4cff62a-664d-4d45-9302-98723eac1319?include=path%2Cproperties%2CallowableOperations%2Cpermissions

In the response
...
{
"authorityId": "GROUP_site_swsdp_SiteManager",
"name": "SiteManager",
"accessStatus": "ALLOWED"
},
...

So the API does not return the display name and someone decided to use the authorityId instead.

I assume that the most correct way to fix this is to include the display name in the API response and use that.

[DenysVuika]

The authorityId is used probably because the names are not unique, i.e. in my case I'm testing, all names are equal to all:

[AlgoJerViA]

All is the name of the role, it is not relevant to this issue.
Look at the difference when I search for groups to add. Then I see the property cm:authorityDisplayName which is of course the only thing I should ever see as the end user. The cm:authorityName and cm:authorityDisplayName can differ completely so I might search and add the group Mothers and then the permissions list would display Fathers instead.