fix: Sorts group mappings in ldap.toml by org_role

[v0nNemizez]

Description

Due to the way Grafana reads group mappings, the mappings needs to be sorted so it reads them in this order: Admin->Editor -> Viewer.

Check List

• A summary of changes made is included in the CHANGELOG under ## Unreleased
• New functionality includes testing.
• New functionality has been documented in the README if applicable.

[bmhughes]

Thanks for the PR @v0nNemizez!

Looks good in principal but it appears to have broken indempotency as the resource is converging on the second run, looks like load_current_value is returning the wrong existing config entry. Could be due to the the helper returning the first match but I'd expect it to work still so you'll need to do some debug there before we can merge this.

[v0nNemizez]

what do you mean here? Im running this on a company test server running against the company AD with nested groups, and this works as intended and sovled our problems:)

[bmhughes]

If you look at the CI tests then you'll see that all the LDAP ones have failed as Kitchen has failed as the run shouldn't converge a second time but it has due to the ldap_group_mapping resource re-ordering the group_dn. It'll be something tied to how this PR changes the sort order.

https://github.com/sous-chefs/grafana/actions/runs/11340425253/job/31536848255?pr=467#step:4:2309

It may work but unfortunately it isn't right :)