Feat/rework-perferences

[ajnart]

rework the preferences screen

more pretty and has a prevention to not go out of the page by mistake with unsaved changes

[deepsource-io]

Here's the code health analysis summary for commits 2354510..e79efe0. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[ajnart]

@Meierschlumpf I addressed the comments. In the end I switched to tanstack form for the form

[Meierschlumpf]

Why not mantine form with integrated zod validation from homarr/form?

[ajnart]

Why not mantine form with integrated zod validation from homarr/form?

I didn't know we had @homarr/form xD

[ajnart]

@Meierschlumpf I moved to homarr form now, feel free to re-review whenever

[Meierschlumpf]

Can you please combine the mutations into one?

[ajnart]

Can you please combine the mutations into one?

This is outside of the scope of this PR imo, we made all of these mutations and used them before.
I tried prototyping a updateSettings procedure using a schema built from the sum of all of the types in https://github.com/homarr-labs/homarr/blob/1bb3654bf7fffa6724d606991b12ea29d7c1d0c8/packages/validation/src/user.ts but it seems like a big refactor because the return type needs to be inferred from what's in the input or not. I'd love to take a look at it in a separate PR tho.