fix(permission): stabilize Read order to eliminate spurious no-op diffs

[Mahanmmi]

A permission with multiple targets (or actions.users / actions.groups) shows a no-op diff on every terraform plan — items swap positions even though nothing actually changed:

targets: [
  ~ [0]: { ~ name: "ANY REMOTE" => "my-repo-local" }
  ~ [1]: { ~ name: "my-repo-local" => "ANY REMOTE" }
]

The cause is in fromResourceAPIModel and fromUsersGroupsAPIModel: the API response is unmarshaled into a Go map, then turned into a slice with lo.MapToSlice before being wrapped in a types.Set. Go map iteration is randomized, so the intermediate slice comes out in a different order on every Read, and that order leaks into state.

Fix: sort the slice by name before calling types.SetValue. Added a small sortAttrValuesByName helper and call it in both spots.

[github-actions]

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

[Mahanmmi]

I have read the CLA Document and I hereby sign the CLA

[soumyas-dev]

Hi @Mahanmmi ,

Thank you for your contribution.

Our CI pipeline issues have been resolved, and we are now accepting contributions again. If you are still interested in submitting this change, please rebase your branch on master and update the CHANGELOG. We look forward to reviewing your pull request.