Function tag ordering is inconsistent across reloads and does not respect datapack ordering

Present in 1.13-pre7

And 1.13-pre8

And 1.13-pre9

And 1.13

And 18w30a

And 18w30b

And 18w31a

And 18w32a

And 18w33a

And 1.13-pre1

And 1.13.1-pre2

And 1.13.1

And 18w43c

And 18w46a

And 18w49a

And 18w50a

and 19w02a

and 19w03a

and 19w03b

and 19w03c

and up to 19w06a

And 19w07a

And 19w08a

And 19w09a

And 19w11a

And 19w11b

And 19w12a

And 19w12b

And 19w13a

And 19w13b

And 19w14a

And 19w14b

And 1.14pre1

And 1.14-pre2

When I was testing my fix for MC-126946, I accidentally hit into issue and found a fix.
Code analysis: (Using FabricMC yarn 1.14 Pre-Release 2+build.5)
(Method Lzb;a(Ljava/util/Map;)V)

public void applyReload(Map<Identifier, Tag.Builder<T>> map_1) {
      while(true) {
         if (!map_1.isEmpty()) {
            boolean boolean_1 = false;
            Iterator iterator_1 = map_1.entrySet().iterator();

            Entry map$Entry_2;
            while(iterator_1.hasNext()) {
               map$Entry_2 = (Entry)iterator_1.next();
               if (((Tag.Builder)map$Entry_2.getValue()).applyTagGetter(this::get)) {
                  boolean_1 = true;
                  // In this line below, the tag builder needs a ".ordered(this.ordered)" call
                  this.add(((Tag.Builder)map$Entry_2.getValue()).build((Identifier)map$Entry_2.getKey()));
                  iterator_1.remove();
               }
            }

            if (boolean_1) {
               continue;
            }

            iterator_1 = map_1.entrySet().iterator();

            while(iterator_1.hasNext()) {
               map$Entry_2 = (Entry)iterator_1.next();
               LOGGER.error("Couldn't load {} tag {} as it either references another tag that doesn't exist, or ultimately references itself", this.type, map$Entry_2.getKey());
            }
         }

         Iterator var5 = map_1.entrySet().iterator();

         while(var5.hasNext()) {
            Entry<Identifier, Tag.Builder<T>> map$Entry_3 = (Entry)var5.next();
            this.add(((Tag.Builder)map$Entry_3.getValue()).ordered(this.ordered).build((Identifier)map$Entry_3.getKey()));
         }

         return;
      }
   }

In my opinion, the best fix is to supply the "ordered" boolean (i.e. call "za$a(Z)V" method) when the tag builders are prepared asynchrously, as order information is available already at that point and this can improve code maintainability.

I sincerely wish mojang can include this fix in Pre-3 and fix MC-126946 as well.

And 1.14-pre3

And 1.14-pre4

And 1.14-pre5