[Feature Request] Group Node editing overhaul.

This is going to be a lot, so bear with me.

I've recently discovered group nodes and have really appreciated how they function. their ability to clean up workflows and practically create new custom nodes using a purely UI interface makes them incredibly powerful tools. despite this, I feel like they are not currently anywhere near their full potential. there are a lot of minor snags and hitches that make what should be a time saving technique into a frustrating time sink.

My suggestion would be a complete rework of how you interface with grouped nodes. Firstly, I propose to completely get rid of this menu
It is a clunky piece of work that just gets more crowded the more complex you try and get with grouped nodes.

in it's place, I suggest that you would replace it's spot on the menu with the option to "enter" a grouped node. Doing this would put you into a new 'sub' workspace which contains the contents of the grouped node. A sub-workspace would have a few key differences to the main workspace

1. all widgets would have a check box to the side which would control whether or not they display in the parent node
2. all unplugged inputs and outputs would have a check box next to them which controls whether or not they get piped out to the parent node
3. all nodes would have a small integer input on the top right hand corner (aligned with the title of the node) defaulted to zero. this would be the "priority" of the node. by default, the parent's input, output, and widget ordering would be sorted how they normally are by default. However, any node can have their priority raised or lowered. higher priority nodes would have their components display lower priority nodes, defaulting to the default ordering when multiple nodes have the same priority.

here is a mock up design of how something like this could look using a KSampler node as example.

there would be a button on the bottom left corner of the screen (next to the debug info) that would bring you up out of a grouped node. additionally, there would be a key combo a user could enter to quickly exit a group node. Doing this key combo with a group node selected would allow a user to quickly enter the group node instead.

I would also suggest that the ability to nest group nodes be implemented along-side this feature. I feel like these two go hand in hand, as having a group node represented as a workflow itself would allow another group node to be nested inside of it. Group Node definitions would still remain in the "root" of the workflow json, since these definitions improve upon re-usability and save on space.

I am well aware that something like this is a lot to ask, but I just wanted to write down my thoughts In a github commit so that if one day I, or someone else, wanted to tackle this, they'd have something to reference.