Un-hardcode multiple canFireProjectile methods

[ZestyBlaze]

A suggestion from Commoble to remove the hard coding on AbstractSkeleton.canFireProjectileWeapon and bind it to a Neoforge functionality tag

Currently only contains minecraft:bow within the tag as that is all the vanilla skeleton checks for, added some javadoc to it but maybe specification that it should be items that extend BowItem is required as Crossbow Logic won't work with skeletons

Also open to better naming suggestions if that's a thought

Following a quick discussion, now contains 3 tags and more patches which also remove the hardcoding on Pillager, AbstractSkeleton and Piglin allowing all of these mobs to now use items from their respective tags, which all point towards the common tag for their respective weapons (Bows for Skeletons and Crossbows for Piglins and Pillagers)

[neoforged-pr-publishing]

• Publish PR to GitHub Packages

[sciwhiz12]

If we're modifying AbstractSkeletons to accept a tag of bows rather than only the singular bow item, should we also modify Pillagers and Piglins for a corresponding tag for crossbows? (We also have a c:tools/crossbow for that.)

[ZestyBlaze]

I'll work on adding a commit for that then and we'll do that in this PR too then I think

[neoforged-automation]

@ZestyBlaze, this pull request has conflicts, please resolve them for this PR to move forward.

[ZestyBlaze]

Welp, I'm now away for a while for a holiday so that's great. I'll rebase it when I'm back