'Workflow Presets' feature to save/load specific values in multiple nodes simultaneously

### Feature Idea

Let's say I have a well established universal workflow for some particular Text To Image model to generate images in various styles, resolutions etc.

The inconvenience is that for some style "A" I have one set of settings (like Lora weights specific values, sampler, scheduler, number of steps, prompt prefix, specific negative prompt etc.); for some other style "B" I might have other settings. I might have dozens of these 'styles', and it is not always efficient to handle this by having either essentially same (but slightly different) dozen workflows, or to have a monstrous workflow with many nodes duplicated in parallel to enable one execution path at a time to achieve different settings combinations.

What would be great to have (just to describe the idea):

- A new "Workflow Preset" function to save/load values in specific nodes in same workflow. For example, ALL nodes which have editable parameters in a current workflow can have a context menu item like "add to Workflow Preset". So I could add KSampler, Positive prompt, Negative Prompt, 2 separate Lora Loaders etc. to Workflow Preset function.
- When I have all nodes I'm interested in stored in Workflow Preset function, I could start creating presets
- For this we could have some "store current state as Workflow Preset" toolbar button. When user clicks this button, a dialog could be shown so that a user could enter a new preset name. When user accepts a new name, editable values of all nodes which were previously "added to Workflow Preset" are stored under this name.
- User could do it multiple times, effectively creating many named presets for their desired settings combinations
- User could recall these presets by simply selecting a named preset from some toolbar.
- If there are 0 nodes in "Workflow Preset" (i.e. user did not select any nodes to store their values) - "add to Workflow preset" button might be inactive with a tooltip "Please add some nodes to Workflow Preset" first.

This would allow to achieve rich 'meta-workflows' with as little as possible spaghettification, while providing a major boost in productivity and convenience.

UPD: I realize 'almost the same' can be done by just having more workflows, but it's not the same.