Added switch Theme Preset

[Tux73]

• Create a new interface IThemePreset to represent a Theme Preset.
• Modified the MudThemeManager component to accept a collection of IThemePreset.
• When select a Preset from UI the theme is update and the Theme manager color palette is force to update also.
• The Theme manager color palette is update also when switch to Dark/Light theme mode.

[sonarqubecloud[bot]]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-advanced-security[bot]]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[ScarletKuro]

Hi,

Thanks for the PR, I really appreciate it. However, this PR includes many unnecessary stylistic and formatting changes.

For example: https://github.com/MudBlazor/ThemeManager/blob/da26ee191acaa1fa4f55a2d29d378a9392f6c43c/src/MudBlazor.ThemeManager/Components/MudThemeManagerColorItem.razor.cs#L28-L29 You moved these properties from the top to after the parameters, but according to our usual convention, they should remain at the top.

There are many other unnecessary changes, such as swapping the positions of ColorPickerView and ThemeManager, as well as significant movement of items in MudThemeManager.razor.cs. Reformatting MudThemeManager.razor also makes it difficult to understand the relevant changes you made.

These kinds of stylistic refactors are only allowed by project members.

When contributing to open-source projects, please avoid making changes outside the scope of your feature. Otherwise, it will be difficult for reviewers to review and most of the time it will be rejected. I'm not trying to be difficult, it's just a standard rule in the open-source community.