This makes it impossible to use tags like "#forge:gears/iron" in recpies without there being an uncraftable variant (if the hammerlib gear recipes are disabled).

Steps to reproduce:

1. Install mods:

• Architectury [9.2.14]
• HammerLib [20.1.33]
• KubeJS [2001.6.5-build.16]
• Rhino [2001.2.3-build.6]

2. Create 'kubejs/server_scripts/test.js` with

ServerEvents.tags('item', event => {
    event.removeAllTagsFrom( /hammerlib:gears.*/ );
})

4. Create a world a give self a gear /give @s hammerlib:gears/iron
5. With gear selected run /kubejs hand and observe that the item still has the tag #forge:gears/iron.
6. Dump kubejs with /kubejs export and observe that local/kubejs/export/tags/minecraft/item/forge/gears/iron.json does not exist despite an item with that tag existing.

Compatibility with KJS tags is not planned right now.

My main concern is somehow being able to remove the tags for the hammerlib gears that the modpack I'm working isn't even using, so that I can use those tags for my one purpose, without things like recipe viewers showing the uncraftable item.