Data component cleanup

[Robotgiggle]

The HEX_HOLDER_PATTERNS and PIGMENT components, used for casting items, are both set when a hex is written into the item and both cleared when the item is erased. There is no situation in which the value or presence of one would change without the other also changing. Thus, there's no reason for them to be two separate components, so this PR combines them into a single component called HEX_HOLDER that stores both a list of iotas and a FrozenPigment.

This will break any casting items that were created in 1.21 worlds before this change, but the 1.21 version is still in alpha so I think that's OK.

Along with combining the components as described above, this PR also:

• fixes Ancient Cyphers not having the Ancient Pigment baked in (I think this just got lost in the port somehow)
• fixes the safety check on creative scrolls now that the ACTION component stores a ResourceKey rather than a ResourceLocation
• fixes a typo when setting the MEDIA and MAX_MEDIA components using ItemMediaHolder.withMedia()
• removes the now unused string constants that previously stored the names of the NBT tags used by casting items, media holders, and the media cube
• adds comments to HexDataComponents explaining where each component is used
• adds comments to ItemSpellbook to explain some of the more complicated if/else trees
• updates the comments in ItemScroll to refer to components rather than tags

[s5bug]

Would there be any value in making this a TreeList? I actually doubt it (I think it would need to be benchmarked) and converting on-use is going to be better than converting on-parse).

[Olfi01]

Wouldn't it be possible to make even alpha versions of items correctly readable by using Codecs?

[Robotgiggle]

How would you do that? The current alpha version uses two separate components, and the new version in this PR uses one component with two fields. I know you can make a codec that accepts input in multiple formats, but that’s still just expecting multiple formats within one data component. Is there some way to make a codec that can decode two separate components into a single object?

[Olfi01]

Right, sorry, that does sound like it might not be possible. What could be an option would be adding another datafixer, but I'll only be able to answer whether I think that's a good idea after I've finished doing it for the 1.20 -> 1.21 migration