Feature Request: Comprehensive Enterprise & Whitelabeling UX Enhancements

What problem will this feature address?

I want to report a few issues in Dokploy that are related to the Enterprise user experience. While recent fixes successfully addressed the branding layout flash, there are still a few areas where Dokploy-specific UI remains visible or layout flashes occur, which breaks the immersion for a fully white-labeled Enterprise instance.

1. SSO Button Flash & Persistence: When a user has a license enabled and active, the "Sign in with SSO" button is injected dynamically after the login page loads, causing an unpleasant layout flash above the email field. Additionally, many organizations do not use SSO at all, yet this button persistently appears on the login screen with no way to hide it.
2. Confusing "Forgot Password" Redirect: In the self-hosted community version, clicking "Lost your password?" correctly redirects users to the Dokploy documentation. However, for a white-labeled Enterprise user (e.g., a team member of "XYZ Cloud"), being sent to docs.dokploy.com is highly confusing. The end-user has nothing to do there because only their internal IT admin can actually help them reset their password.
3. Hardcoded Social Icons: The login and onboarding pages hardcode social icons (GitHub, X, Discord). It is not necessary for every business to have all three of these active based on their region or needs. For a white-labeled instance, linking to external platforms can easily break the team's branding.
4. Sidebar Documentation and Support: The sidebar allows adding custom documentation and support links, but some rebranded instances do not have their own custom pages and simply want to hide these links entirely to keep the interface clean.
5. Theme-incompatible Custom Branding: Dokploy's default branding beautifully supports two different states (dark and light) for the logo and favicon based on the system theme. However, custom Enterprise branding only provides a single setting. This means a dark logo might become completely invisible when the system switches to dark mode.
6. Dashboard Width Inconsistency: There is a noticeable inconsistency in the layout width of the dashboard's body. Pages in the "Home" section (and a few others like "Sessions" and "Audit Logs") utilize the full available width. However, most pages under "Settings" (like Profile, Web Server, Deployments) use a narrow max-w-5xl container, making them appear awkwardly constrained compared to the rest of the app.

Describe the solution you'd like

These are all small, independent enhancements aimed at stabilizing the Enterprise UX without breaking existing functionality or requiring major refactoring:

1. SSO Toggle & Fix: Prevent the SSO button from flashing by resolving its state before the page renders. Add a toggle in the settings to completely hide the SSO button when it is not being used.
2. Custom Forgot Password Flow: Allow Enterprise instances to configure a custom forgot-password message/instruction and provide a custom contact email. Instead of redirecting to the docs, it should open a custom section guiding the user on what to do next. We can add a custom "Contact Support" button that acts as a mailto: link, storing the support email so the user can reach out with one click. (Note: Since administrators can already use the dokploy reset-password <email> CLI command to reset a user's password, this workflow is perfect).
3. Social Icons Toggle: Add a simple configuration toggle to allow admins to hide the social icons on the login page.
4. Sidebar Toggles: Add separate toggles to hide the Support and Documentation links in the sidebar. If both are hidden, the entire "Extra" section in the sidebar should automatically hide.
5. Dark/Light Theme Logos: Provide an extra optional setting for a dark-mode logo and dark-mode favicon to enhance branding. Backward compatibility: If the optional dark variants are not set, it should gracefully fall back to using the current single user-set light logo/favicon for both themes, ensuring nothing breaks for existing users.
6. Standardize Settings Width: Remove the narrow max-width constraints on the specific Settings pages so their width matches the full-width layout of the Home pages, ensuring complete UI consistency.

Additional context

Open Questions for Maintainers: @Siumauricio and @narcisonunez
Waiting for your review to share your options on these, so I can start working based on priority or work on all!

Will you send a PR to implement it?

Yes, I will send separate PRs for each targeted point as they are grouped together based on work targets and priorities.

Split the request into the six targets named in the issue and start by locating the login, onboarding, sidebar, branding, and Settings page entry points, along with the existing Enterprise configuration. Treat the reset-password CLI command as context for the forgot-password flow. Done means each targeted enhancement has a focused implementation and preserves the stated fallback behavior and existing functionality.