Cleanup tailwind colors

[anbraten]

We currently have several places defining colros tailwind.css, style.css making it extremely difficult to adjust colors.

Steps

• Are color variables like --stroke-wp-error-100 actually used, otherwise remove them
• Avoid colors from being mapped differently for light and dark mode: :root[data-theme='light'] { in style.css, if a color should be different in dark mode use dark:bg- modifier instead
• verify that color steps are actually based on saturation levels 100, 200, 300, ...

[anbraten]

@qwerty287 Since it looks like you've done the migration to Tailwind v4, do you have any additional details about the mentioned parts?

[qwerty287]

The colors were all present before as well, weren't they?

[xoxys]

Colors are not "defined" in multiple locations. style.css does not define colors, it is just using vars and the main purpose it to allow custom theming by users. I'm a bit unhappy that we go back and forth quite often with this entire color/css structure discussion. I would like to finally find a consensus on this part and avoid refactoring every few months.