"Model" Item NBT Field

I'd like to request a new optional NBT field for items that's simply called Model. Example - The following code would give you an apple that looks like a carrot:

/give @s apple{Model:"minecraft:item/carrot"}

This would accomplish the same thing as what we can already do with CustomModelData: overwrite the "minecraft:item/apple" model with an override that accepts custom model data and points to the "minecraft:item/carrot" model, then give yourself an apple with the appropriate CustomModelData.

So why should this "Model" field be added?

- Streamlining. As you saw with what I just wrote, adding a custom model to an item is FAR more clunky than the simple command I wrote at the top. (Also, switching default Minecraft textures around would be achievable without any resource packs). But there's a much more important reason:

- Cross-Pack Compatibility. When using multiple resource packs (for example, playing multiple big custom-item datapacks at once), the resource packs can conflict and overwrite each other. If two packs add custom model overrides to the same item, you'll only ever see the effects from one resource pack at a time. With this new Model field, we wouldn't have to overwrite the vanilla models at all.

Example: /give @s apple{Model:"myresourcepack:item/upgraded_apple"}

All that's needed in this case is for you to have a resource pack that defines a model called "myresourcepack:item/upgraded_apple" - and if it doesn't exist, the apple will continue to just look like an apple.