Husk entity file can no longer be made backwards compatible

General context

Client entity files defined in resource packs use a minimum engine version to know which file is going to be used on marketplace version locked templates. The drowned, for example, has a minimum engine version of 1.16.0, so that definition is only parsed on worlds that are set to version 1.16.0 or higher, and otherwise fall back to the v1.0 definition.

If a file has a different minimum engine version from the other definitions for that same entity, all the relevant fields must be included, even if they are the same as the earlier versions (textures, models, materials, animations, variables, controllers, spawn egg).

Most of the older mobs have a minimum engine version of 1.8.0, which is from before version locking was added. The earliest version with this feature is 1.13.0, which means these files are always loaded on version locked worlds.

However, as of version 26.0, the Husk client entity was modified for version 1.21.130 to use a minimum engine version of 1.12.0, so resource packs that use it can no longer properly support version locked worlds.

Including a husk entity definition with the minimum engine version set to 1.12.0 will always completely overwrite the vanilla files in version locked worlds, and including one with the minimum engine version set to 1.8.0 will be overwritten by the vanilla file instead on worlds with version 1.21.130 and higher.

Steps to Reproduce:

1. Download and apply the attached resource pack

2. Create a normal world

3. Grab a husk spawn egg

   ✔ It looks normal

4. Import and create the attached template

5. Grab a husk spawn egg
   ❌ It is invisible

Observed Results:
The husk file in the vanilla_1.21.130 resource pack changes the minimum engine version to 1.12.0.

Expected Results:
The husk file in the vanilla 1.21.130 resource pack keeps the minimum engine version as 1.8.0.

Notes: There is no reason for an updated entity definition to increase the minimum engine version to one that’s also old, if any breaking changes are made it should use the current version.