[Feature Request]: Hop GUI - allow duplication of environments

### What would you like to happen?

I suggest to add a button in the Hop GUI toolbar that allows duplication of (Project Lifecycle) Environments, i.e. to create a new environment that has the same settings of the current one (except the name).

The user could then re-map the settings (especially the configuration file paths) to match the context for the new environment (e.g. switching from development to production), instead of reselecting those files one by one.

Why this suggestion? Because I actually feel more confident in patching the `hop-config.json` file directly to create a new environment, rather than reselect the new configuration files one by one (and possibly missing some of them) 😅

_Warning: check if this proposal conflicts with #4881_

### Issue Priority

Priority: 3

### Issue Component

Component: Hop Gui

Start by tracing the Hop GUI toolbar and Project Lifecycle Environment settings, then inspect hop-config.json and compare the proposal with #4881. Done means a toolbar action creates a new environment with copied settings except its name, while allowing paths to be remapped.

Written by the indexing model from the issue text.