Default environment selection & improved environment switching UX

What problem will this feature address?

Currently, when opening a project, no environment is auto-selected—even when a project contains deployments in a specific environment such as production. This leads to confusion because:

• Users expect the environment that contains deployments (e.g., production) to be selected by default.
• The autogenerated production environment cannot be changed, yet it is not auto-selected.
• When working with multiple environments (e.g., develop, staging, etc.), users always need to open a dropdown to switch, which adds friction and requires multiple clicks.
• It’s not immediately visible which environment is currently active.

This slows down workflows and makes navigation less intuitive.

Describe the solution you'd like

Introduce a default environment that Dokploy auto-selects when opening a project.

• If a project has deployments in one environment (e.g., production), auto-select that environment.
  • Otherwise allow users to set their own default, such as develop, which many users start with.
  • Make the active environment more visible without requiring a dropdown.
• Reduce the number of clicks needed to switch environments, e.g.:
  • Tabs for environments,
  • or a sidebar list,
  • or persistent environment buttons

Describe alternatives you've considered

Manually selecting the correct environment from the dropdown every time (current behavior).
Naming environments differently, but this does not solve the UX issue.

Additional context

No response

Will you send a PR to implement it?

Maybe, need help

Start at the project-opening flow and current environment dropdown, tracing how deployments and environments are loaded and selected. Done means a sensible default environment is selected, the active environment is visible, and switching between environments requires fewer clicks; the issue does not name specific files or tests.