[MCM-1449] Range specification inconsistency

Partner Rank: 4
Partner Team Reporting: Blockception
Verification builds: 1.17.40

Summary:

Range inconsistency, There are thus far 3 supported range formats. And it's unknown if everywhere were a range is all 3 of them are supported; Suggested to remove 1, or more.

The 3 found formats:

{
 "range_1": [0, 1], //Range is specified as an array with the [min, max] format
 "range_2": { "min": 0, "max": 1 }, //Range is specified as an object with properties min and max
"range_3": { "range_min": 1, "range_max": 2 } //Yet another range specification
 }

Suggested to remove supported for range_3 and replace all with

{ "min": 0, "max": 1}

format.

Impact:

Good examples for the community to use.
Correct working vanilla data-driven files.

Repro Steps:

Observed Results:

Expected Results:

Correct, consistent vanilla files that not only follows minecraft readable format but also by written convention/documentation.

Screenshots/Videos attached: No

Regression Builds: N/A

Notes:

Suggested course of action:
Replace `range_min` with `min`.
Replace `range_max` with `max`.

Files:

behaviorpack/entities/donkey.json
behaviorpack/entities/evocation_illager.json
behaviorpack/entities/goat.json
behaviorpack/entities/hoglin.json
behaviorpack/entities/horse.json
behaviorpack/entities/iron_golem.json
behaviorpack/entities/llama.json
behaviorpack/entities/mule.json
behaviorpack/entities/panda.json
behaviorpack/entities/piglin_brute.json
behaviorpack/entities/piglin.json
behaviorpack/entities/pillager.json
behaviorpack/entities/ravager.json
behaviorpack/entities/skeleton_horse.json
behaviorpack/entities/strider.json
behaviorpack/entities/tnt.json
behaviorpack/entities/vindicator.json
behaviorpack/entities/witch.json
behaviorpack/entities/witch.json
behaviorpack/entities/zombie_horse.json