Refactor Character / Stage Operations To Extend A Shared Parent

[Inferno214221]

Both should be defined as classes which inherit from an abstract Mod class, similar to how each dialog was refactored to extend Dialog. Although both Character and Stage operations are very similar, they also differ enough that most methods need to be adjusted in some way. To allow them the extend a shared parent, contained functions should be split into several smaller ones (Although this is something that should have already been done regardless).

[Inferno214221]

After this, an additional mod type could be incorporated: Assists because they have a very similar format, although they are significantly less popular. Edit: although I haven't looked into it, apparently most of the mod formats are very similar, although with a similar situation about popularity.

[Inferno214221]

Just looked into implementing this with Mod and Mod List classes but encountered a selection of issues:

• There are no asynchronous constructors, which makes sense but all of the planned objects need asynchronous information retrieval for initialisation.
• IPC reduces objects to primitive data types only (objects lose their methods and would have to be reinitialised).
• These classes can't be exposed to the front end due to their use of Node APIs. Only interfaces or wrappers should be used for the front end.
• Methods can't be static and abstract so the abstract Mod class can't mandate static builder functions.

It might still be possible to do this with Manager classes which utilise the existing interfaces.