dsContributor shows up in list role assignments result but not in user interface

What steps does it take to reproduce the issue?
This assumes your dataverse collection is configured to allow all authenticated users to create datasets.

Choose a dataset and retrieve the role assignments on that dataset through the API. Note that the following role assignment is included:

 {
   "id": 12345,
   "assignee": ":authenticated-users",
   "roleId": 5,
   "_roleAlias": "dsContributor",
   "definitionPointId": 1
 }

Note also that the only permission in this role is AddDataset, which is only useful for dataverse collections, as you cannot create a dataset within a dataset.

Now for comparison:

1. Log in as admin
2. Open the same dataset
3. Go to Edit Dataset -> Permissions -> Dataset
4. The role assignment ":authenticated-users" -> "dsContributor" is not included

• What did you expect to happen?
  I should expect the role assignment to be included in both the API result and the UI or in neither. Since the role assignment has no practical effect on the dataset that inherits it, it is probably best not to include it.

Which version of Dataverse are you using?
5.10.1

Any related open or closed issues to this bug report?
N/a

Start with the dataset role-assignment API response and the Edit Dataset → Permissions → Dataset UI described in the reproduction steps. Compare how the dsContributor assignment for :authenticated-users is handled in each path, then confirm the chosen behavior with a regression test covering the API result and UI list.