[NT-409] Fix issue with feature flags ordering

[dusi]

📲 What

#877 has recently broken the way we can toggle feature flags ON and OFF so this PR fixes that.

🤔 Why

The toggling was previously broken due to sorting only being applied to the data source (not the actual data being sorted).

reloadWithData did get the sorted array while updateConfigWithFeatures did not ... therefore when the data was fetched from the server in un-sorted order it would cause weird behaviour (the data displayed would not reflect the data being toggled ON/OFF).

🛠 How

This PR should fix that by both applying sort to updateConfigWithFeatures as well as adding tests to cover this case.

✅ Acceptance criteria

In order to test this we should test both scenarios. For that please put the following code in FeatureFlagToolsViewModel.swift on line 46.

Since the feature toggles are returned in random order you might need to run the app couple times.

.map { configFeatures in
  var features = [FeatureEnabled]()

  for (key, value) in configFeatures {
    guard let feature = Feature(rawValue: key) else {
      continue
    }

    features.append((feature: feature, isEnabled: value))
  }
  print("*** features: \(features)")
  return features
}

A) Feature toggles are received in alphabetical order

• Verify that feature toggles are printed in alphabetical order (the above print statement)
• Toggle feature toggles ON and OFF and double check they're affecting app's behaviour (proper native checkout flow)

B) Feature toggles are not received in alphabetical order

• Verify that feature toggles are printed in non-alphabetical order (the above print statement)
• Toggle feature toggles ON and OFF and double check they're affecting app's behaviour (proper native checkout flow)

[dusi]

You can see that previously reloadWithData would get sorted array while updateConfigWithFeatures would not ... this should be fixed now

[cdolm92]

Thanks for fixing! looks good to me 🎉