Fix expression parse order

[TPGamesNL]

Description

The order of the Skript#expressions field was partially reversed:
https://pastebin.com/auvMwfnc: Registered is the order it was registered, Detected is the order of the list after registration. Note that the order of registration shouldn't exactly match the order of the list, as expression with the same ExpressionType should be grouped together. Also note that ExprDamageCause is registered earlier due to BukkitClasses#L1302.

This is the new result: https://pastebin.com/b41zBNrV

---

Target Minecraft Versions: any
Requirements: none
Related Issues: none

[FranKusmiruk]

I am failing to understand how this changes aynthing at all? Or is it only useful to those who make use of the pre load event to change order?

[TPGamesNL]

I am failing to understand how this changes aynthing at all? Or is it only useful to those who make use of the pre load event to change order?

For example, if you have two expressions with the same ExpressionType: ExprA and ExprB. You register ExprA before ExprB. If there is a string matching both expressions (patternwise and init-wise), you'd expect ExprA to be chosen (since it makes more sense with the order of registration, and because that's how all other eyntax elements work), but ExprB will be chosen instead.
This would be very rare to come across however, because this doesn't apply to two expressions with differing ExpressionTypes, they are (relatively) in the right order.