Add TalismanActivateEvent (Updated version of #3920)

[JustAHuman-xD]

Description

I've made this pull request to update and apply some suggestions from #3920
I also have a couple of ideas of things to add to the PR but I'm going to ask for opinions on those beforehand

Proposed changes

• In `Talisman#trigger(Event, SlimefunItem, boolean) I changed the logic behind using ender talismans
  • Instead of passing the normal talisman to the Talisman#activateTalisman method it now passes the ender talisman's talisman (mouthful I know)
  • The reason behind this change is to ensure that TalismanActivateEvent#getTalisman will properly reflect wether an ender or normal talisman was used
• Added the TalismanActivateEvent
  • Extends PlayerEvent and implements Cancellable
  • Called when any talisman is activated by the Talisman#activateTalisman event
  • Contains The Player, Talisman, and ItemStack used when activating a talisman
• In Talisman#activateTalisman call the new event
  • if the event is not cancelled continue with normal operations
  • only consume the talisman if the event preventsConsumption is false (which is the default value)
• Added TestActivateTalismanEvent (Blame sfiguz for any problems with it (half joking))
  • Tests that the event properly fires for normal and ender talismans
  • Tests that the event has the expected fields with normal and ender talismans
  • Tests that the event can be cancelled
  • Tests that the event can prevent consumption

Related Issues (if applicable)

N/A

Checklist

• I have fully tested the proposed changes and promise that they will not break everything into chaos.
• I have also tested the proposed changes in combination with various popular addons and can confirm my changes do not break them.
• I have made sure that the proposed changes do not break compatibility across the supported Minecraft versions (1.16.* - 1.20.*).
• I followed the existing code standards and didn't mess up the formatting.
• I did my best to add documentation to any public classes or methods I added.
• I have added Nonnull and Nullable annotations to my methods to indicate their behaviour for null values
• I added sufficient Unit Tests to cover my code.

[github-actions]

Your Pull Request was automatically labelled as: "🔧 API"
Thank you for contributing to this project! ❤️

[JustAHuman-xD]

The couple of ideas I had that I wanted opinions on:

• Adding a field to the event that controls whether or not the talisman should be consumed
• (I had another one but have currently forgotten it)

[github-actions]

Slimefun preview build

A Slimefun preview build is available for testing!
Commit: c43dad64

https://preview-builds.walshy.dev/download/Slimefun/4045/c43dad64

Note: This is not a supported build and is only here for the purposes of testing.
Do not run this on a live server and do not report bugs anywhere but this PR!

[Sfiguz7]

Requesting change as I don't see a reason not to add the optional preventConsumption flag. Adding a test request while I am at it

EDIT: Justin added the needs testing already

[Sfiguz7]

Spent some time in VC and all looks good, especially the tests <3

[J3fftw1]

can we also have tests that the endertalisman doesnt work in a normal inventory and for the normal talisman not to work in an enderchest

[Sfiguz7]

Don't worry about the list of commits above, for some reason I was unable to push to Justin's fork and I am an impatient blueberry so I copied over my changes a piece at a time. Also didn't know about batch committing suggested changes so there you go

[J3fftw1]

Looks good to alessio