Correct enumdata.py's new-at-v42 entries to match generated data

Amends commit 9a8b9473d5 - apparently
the enumdata.py entries were tidied up after the data had been
generated, leading to them being inconsistent (and I missed that in
review). That, in turn, meant the next update would have changed the
public API enum members, backwards-incompatibly; so make enumdata.py
consistent with the released public API. We'll be tidying the order up
at Qt 7 in any case.

Task-number: QTBUG-110333
Change-Id: I3eed2924ce8b69deb552e923d9b0dc142c5f3a65
Reviewed-by: Konrad Kujawa <konrad.kujawa@qt.io>
Reviewed-by: Mate Barany <mate.barany@qt.io>
Reviewed-by: Ievgenii Meshcheriakov <ievgenii.meshcheriakov@qt.io>
(cherry picked from commit 4e23da9086)

util/locale_database/enumdata.py

@@ -361,12 +361,12 @@ language_map = {
     329: ("Nheengatu",                   "yrl"),
     # added in CLDR v42
     330: ("Haryanvi",                    "bgc"),
-    331: ("Moksha",                      "mdf"),
-    332: ("Northern Frisian",            "frr"),
-    333: ("Obolo",                       "ann"),
-    334: ("Pijin",                       "pis"),
-    335: ("Rajasthani",                  "raj"),
-    336: ("Toki Pona",                   "tok"),
+    331: ("Northern Frisian",            "frr"),
+    332: ("Rajasthani",                  "raj"),
+    333: ("Moksha",                      "mdf"),
+    334: ("Toki Pona",                   "tok"),
+    335: ("Pijin",                       "pis"),
+    336: ("Obolo",                       "ann"),
 }
 
 language_aliases = {