Approval rules not being applied correctly by Gitlab

If protected branches are being used as part of approval rules, ie applying a rule to specific branches, if the branches in the rule are in a different order to what they are in gitlab, GPC will seemingly see this as a change to the settings, making it try to apply the members as if they were different to what is currently there, but since no members need applying they are all considered errors.

The management of protected branches with regards to approval rules should not care about the order of the protected branches, like what is done with members, this uses a difference of two sets.

The config still applies successfully since GPC doesn't need to configure the members or the protected branches of an approval rule, they are just in a different order. However, the job still fails because of the raised error. As a side effect of all this, the error is technically incorrect since it only refers to members and not the branches, but this is because of the branches causing the members management to trip up, raising the error.