[Feat]: UI improvement: separation of things that are separate

[ppbrown]

Describe your use-case.

As a new user, it looks like there is a single config, and everything is unified.
This is because there is a single, top level "config" control menu pair, and a single long tab-like bar across the second row down.

This actually caused me to misunderstand the workflow of OneTrainer for quite a while.
The "Concepts" stuff is completely separate from the other config, and has its own save thingie.

I wrote a newbie guide on my experiences on OneTrainer, and someone wrote to me asking, "how do you manage concepts?"
They didnt realize it was even possible to save out concept sets. Neither did I for quite a while. Because I saw the "save current config" button.. and there was nothing else at that level.. so I figured that was the only save button

What would you like to see as a solution?

Suggest two changes that work in tandem.

1. Split the single tab bar, so that the concepts is in a section by itself.
   It can still switch the main area view like it does now, and still be in mostly the same place. But just putting the tab-enable button in a separate section, would make it much clearer that it is, indeed, separate
   eg:
   Instead of

[general][model[concepts][.....]

have

[general][model][...] _space_ [concepts]

2. have the main "save config" buttons be similar to the "save concepts" buttons, and be at the same level.

When you have two separate save buttons visible at the same time, it is then immediately clear to the user they are two separate things to save.

Have you considered alternatives? List them here.

No response