PatternElement Combinations + Conflicts Test

[Absolutionism]

Problem

As Skript progresses further, adding more elements and patterns, ensuring minimal pattern conflictions can become increasingly harder to maintain with each new pattern added.

Solution

Adds getAllCombinations and abstract getCombinations to PatternElement to construct all possible combinations that can match.
Adds JUnit PatternConflictsTest ensuring getAllCombinations correctly operates with manual inserted patterns and combinations.
Additionally, this JUnit will go through every single registered element and it's patterns to construct all combinations, store them and check if a combination can be used for more than one element/pattern.

Testing Completed

JUnit

Supporting Information

TODO:
Some form of exclusion if only x and y then exclude as can be seen with ExprScriptsOld and ExprScripts since only one can be usable at a time due to experiment enabling.

Categorize the elements, so patterns used in Structures don't get marked as conflictions with Expressions or Effects

---

Completes: none
Related: none

[Efnilite]

missing docs on all the methods. especially init should have a very clear overview of what happens. see the function rework's FunctionArgumentParser for an example

great addition 🔥

[APickledWalrus]

Just about ready