Refactor how PoB handles item types and subTypes

[QuickStick123]

Description of the problem being solved:

GGG uses classes and categories internally, for example in PoE 1 A Sceptre is a class called Sceptre and a category called One Hand Mace. As we have our own special type/subType system it become annoying to make mapping between these formats and they have to be manually manged which can lead to issue such as when we ported our changes to PoE 2. GGG is not super consistent with labels and while this isn't a problem so much in PoE 2 due to most items having their labels it is problematic in PoE 1 e.g. abyss jewels uses a special label that must be hard coded which makes it easier to just hard code all labels.

This also automatically handles different item stat types, now called the type catgory which refers to wether is a evasion/es/armour equipment.

There is an issue that isn't super desirable is that all jewels are considered to be of the same class so they all get squashed together now. The label Charm: Utility Flask isn't very nice either.

Todo:

• The influence stuff should probably be fixed and commented out if we want to port this to PoB 1.
• Need to double check usage of class vs category is correct across the program.
• Fix issue regarding being unable to distinguish between radius jewels and regular jewels, this is problematic for mods leaching onto regular jewel tags for trade stuff. This could be fixed by properly supporting them though so they are distinguished but a solution here would be good. This could be done by readding the type directive to be used sparingly in cases where GGG doesn't provide enough clarity.
• Check the rare stuff works

Before screenshot:

After screenshot: