Explain why we need to do things differently at times, to serve as a
reference.

Groups graphics audio and system settings together in a way that
reflects the frontend. This also just conceptually groups them more
nicely than they were.

Also adds a couple characters that denotes the state of the setting.
M for modified, or not default.
C for custom, in context of per-game settings.

Gives every option of the enums a string literal via a macro.

Reduces code bloat a good bit by moving code specific to each sub widget
to their own functions.

Starting with combobox

Putting code specific to the sub-widget in their own function.

Dark theme mandates a 100px minimum width for QAbstractButton, even
though this is not desired here.

Odd issue happens that dragging the cpu or system tabs in custom configs
would cause the window to take up the entire verticle space of the
screen.

Makes comboboxes always correspond to the value of the setting they're
modifying.

Needs a considerable amount of management specific to some of
the comoboboxes due to the audio engine configuration.

general: Partial audio config implmentation

configure_audio: Implement ui generation

Needs a considerable amount of management specific to some of
the comoboboxes due to the audio engine configuration.

general: Partial audio config implmentation

settings: Make audio settings as enums

This one looks more relevant on Windows.

Makes checkbox creation an option as opposed to a label.

It's empty.

These don't need to be whole new types.

To specialized a setting to be worth adding to the shared_widget imo,
so add it roughly like before.