"max" is ordered before "min" by the JSON data generator

Background

22w18a introduced a technical change that the data generator now orders JSON entries in alphabetical order (with the exception of `config` and `type`).

The Bug

This change has caused `max_inclusive`, `max_exclusive` and similar entries to be placed before `min_inclusive` and `min_exclusive` in default JSON files, causing confusion.

Example:

"data": {
                "type": "minecraft:uniform",
                "value": {
                  "max_inclusive": 3,
                  "min_inclusive": 0
                }
              },

Steps to reproduce

1. Download the vanilla worldgen files from https://github.com/slicedlime/examples/blob/master/vanilla_worldgen.zip

2. Examine the file worldgen/configured_feature/cave_vine.json

3. Notice that max_inclusive is placed before min_inclusive in all cases.