Add non_color_options to mcprep base data json

[TheDuckCow]

It's another "one more thing" sort of thing, but the automated release script takes a step to refresh the json update. That is done via the line python mcprep_data_refresh.py -auto in the push_latest script. This pulls data from mcprep_base_data.json file before dynamically filling out the remaining values from Mineways/jmc2obj latest master versions & the latest local Minecraft game jar.

Before this change, I had auto committed the refresh mappings (as I often do) and then saw errors like these in automated tests:

Traceback (most recent call last):
  File "/Users/patrickcrawford/Documents/gits/mcprep/MCprep_addon/tracking.py", line 679, in execute
    raise RuntimeError(self.error_report)
RuntimeError:   File "<addon_path>/prep.py", line 262, in execute
    res = generate.matprep_cycles(
  File "<addon_path>/generate.py", line 356, in matprep_cycles
    res = matgen_cycles_principled(mat, options)
  File "<addon_path>/generate.py", line 1472, in matgen_cycles_principled
    texgen_specular(mat, options.passes, nodeInputs, options.use_reflections)
  File "<addon_path>/generate.py", line 1011, in texgen_specular
    res = util.apply_noncolor_data(nodeTexSpec)
  File "<addon_path>/util.py", line 77, in apply_noncolor_data
    options = env.json_data["non_color_options"]
KeyError: 'non_color_options'

Now all is resolved:

-------------------------------------------------------------------------------
bversion   	ran_tests	ran	skips	failed	errors
-------------------------------------------------------------------------------
(4.2.0)   	all_tests	69	2	0	No errors
(4.0.2)   	all_tests	69	2	0	No errors
(3.6.2)   	all_tests	69	2	0	No errors
(3.5.1)   	all_tests	69	2	0	No errors
(3.4.0)   	all_tests	69	2	0	No errors
(3.3.1)   	all_tests	69	2	0	No errors
(3.2.1)   	all_tests	69	2	0	No errors
(3.1.0)   	all_tests	69	2	0	No errors
(3.0.0)   	all_tests	69	2	0	No errors
(2.93.0)   	all_tests	68	3	0	No errors
(2.90.1)   	all_tests	68	3	0	No errors
(2.80.75)   	all_tests	67	4	0	No errors
tests took 274s to run, ending with code 0

[TheDuckCow]

Just calling out that the original problem was that this structure was removed entirely, since I gather it was at one point manually edited in a commit. Now, it is just moved up above since it's generated from the base mcprep json file.

[TheDuckCow]

FYI @StandingPadAnimations in case it ever comes up, that we should never directly edit the mcprep_data_update.json file since it's generated, and perhaps we should add more safeguards in place to prevent the temptation. Updates should go in the mcprep_base_data file or in the script used to generate the combined updated mcprep_data_update.json file.