Enhanced FeatureGroup

[Tuesday1028]

ModuleGroup is defined by ArchiveModule where the Feature is located.
ModuleGroup is used as the default FeatureGroup instead of AssemblyGroup, and uncategorized Features should be placed in ModuleGroup.
In the Feature, it is possible to define whether to use ModuleGroup as the ParentGroup.
If ModuleGroup is used as the ParentGroup, the Group created in the Feature will be treated as a SubGroup of the ModuleGroup.
If ModuleGroup is not used as the ParentGroup, the FeatureGroup will be created using the existing method without creating a SubGroup.
This approach prevents the main page from becoming too cluttered and allows for differentiation of functionalities among different Modules.

Using ChatGPT for translation, there may be some unclear or incorrect expressions.

[AuriRex]

The entire Group system is a bit awkward and a bit janky.
Maybe it'd be a good idea to make Groups be able to be children / SubGroups of any other Group instead.
Could definitely also change the behavior for "normal" Groups used by Features to be inside their own Group per mod by default too, yes.

I'll look into it 👍