Deleting a user does not remove assigned roles

What steps does it take to reproduce the issue?

• When does this issue occur?

1. Assign a role to user within a Dataverse Collection.
2. Delete the user.
3. Try to create a new subcollection.
   while :InheritParentRoleAssignments is true for the parent collection.

• Which page(s) does it occurs on?
  Create new Dataverse.

• What happens?
  

• To whom does it occur (all users, curators, superusers)?
  Anyone with the permission to create a new Dataverse Collection.

• What did you expect to happen?
  Deleting a user should properly remove all assigned roles (or at least give a warning).
  The assigned role was only visible through the API, and not in the UI.
  Removing the assigned role manually via API fixed the error.

Which version of Dataverse are you using?
6.1

Any related open or closed issues to this bug report?

Screenshots:

No matter the issue, screenshots are always welcome.

To add a screenshot, please use one of the following formats and/or methods described here:

• https://help.github.com/en/articles/file-attachments-on-issues-and-pull-requests

Are you thinking about creating a pull request for this issue?
Help is always welcome, is this bug something you or your organization plan to fix?

Reproduce the issue by assigning a collection role, deleting the user, and creating a subcollection with InheritParentRoleAssignments enabled. Trace how user deletion handles role assignments and compare the API-visible state with the UI; done means deleted users leave no assignments that block subcollection creation, or the deletion flow warns about them.