Switch gitlab_group.ip_restriction_ranges to set to prevent endless diff

Heidi Berryrequested to merge
ip-range-ordering into main

This change modifies how IP restriction ranges are handled for GitLab groups. Previously, the system treated IP addresses as an ordered list where the sequence mattered, but now it treats them as an unordered set where only the unique values matter, not their order.

The main improvements include:

  • Changed the data structure from a list to a set, which prevents duplicate IP addresses and makes the order irrelevant
  • Updated the test cases to reflect this new behavior, where IP addresses can be in any order
  • Modified the comparison logic to sort both the expected and actual IP addresses before checking if they match, ensuring tests pass regardless of the order the addresses are stored or retrieved

This makes the feature more robust and user-friendly, as users don't need to worry about maintaining a specific order when specifying IP restriction ranges for their GitLab groups.

Fixes #6671 (closed)

Merge request reports