ewoks install: pixi always installs the default environment #355

Issue

• ewoks convert stores the pixi workspace files (pixi.toml + pixi.lock) for any environment of the workspace, including named ones (.pixi/envs/<name>). ewoks install always runs pixi install without -e, so a workflow converted from a named environment is reinstalled as default, which can have different packages.
  • Note: pixi uses the same lock file for different environments in the same project. We are not currently saving information about which environment ewoks was run from, so we might not recreate the correct environment.

Proposed Change

• store the environment name in the manager section and install the pixi environment with -e <name>.