MekaTool Radial Profiles

[mewacaser]

Changes proposed in this pull request:

So I got this idea from Mekanism-Feature-Requests#282

It is mostly working and it is awesome to use.
Currently limited to 6 profiles and while it has to be hardcoded to be in the enum there is no reason there couldn't be more, and potentially even disable them based on a numeric property

That being said there are issues with how I did it that probably need to be fixed.
The server sync kinda just piggybacks off of the module.save currently which works, but isn't ideal.
It's currently dealing with the NBT directly instead of using the config.set methods so that the module.save doesn't overwrite it, I have some potential solutions in mind, but I'm not sure which way would be best.
It only saves an option which you have changed while on that profile. Which if there was a way to clear a profile could actually be a feature.
The save button in the GUI doesn't do anything right now.
The profile names can be changed with the GUI, but it's static so it's the same for every MekaTool.

This also kinda makes the handle mode key option on the tool modules obsolete. So we might want to remove that on them.

[Tyrannicodin]

6 seems a good number to me, and we could maybe use the handle mode key to open the menu instead of switching modes if it'll just be obsolete.
As for nbt storage, we might want to store it globally for all meka-tools, because if you're using on meka-tool and switch to another (no clue why you'd do that), you would still want to be able to use your configs.

[mewacaser]

To clarify the handle mode key option previously decided if trying to change the mode would change the mode on that module, the key itself is still being used for the radial menu, but it can change the mode for any config. What I was suggesting possibly removing was just the boolean on the module to say whether it handled the key.

The NBT profiles are currently on the itemstacks, which is also where the module data is, if you switched to a different mekatool it could have different modules/configs/profiles. I don't think we'd want that to be global, even though the profile names are currently.

[Tyrannicodin]

I see what you mean now, and I definitely agree. You're probably right about radial wheels being NBT not global as well

[SirEndii]

It is mostly working and it is awesome to use.

Show me <:

[mewacaser]

minecraft-1182-singleplayer-2022-05-07-13-40-25-xisvz1or-ygwc47bp_Ax91Gc9x.mp4

[mewacaser]

I think everything is resolved on this except for the static mode names. I don't see a way to fix that so I think it's done unless someone else can think of something.
Edit: Forgot about the commented lines I left in there in case syncing the state to the current mode was something we wanted.
Currently you can change the configs however you want and not corrupt the current profiles, you would have to press the save button for that specific profile and it will save the current options to it. The question is whether we want to have changing the options in module tweaker save to the current profile or not? And whether it should be initiated by the client (more traffic) or the server (less configurable)? If it's on the client it could actually be a config option whether or not to sync, which might be nicest for the users.