Activation fails when using env prefix

[wlhjason]

Thanks for creating this handy plugin!

After setting a Conda environment prefix as per the docs here and running hatch env create, I am seeing an error that looks like

EnvironmentLocationNotFound: Not a conda environment: /path/to/cwd/project_default_3.8

Digging into the implementation, it looks like this is because conda activate isn't using the prefix:

hatch-conda/hatch_conda/plugin.py

Line 246 in 5cdeccc

cmdl = f"{self.config_command} activate {self.conda_env_name}"

[OldGrumpyViking]

Yes this should probably be wrapped in a prefix check:

if self.config_prefix is not None:
    cmdl = f"{self.config_command} activate {self.config_prefix}" 
else:
    cmdl = f"{self.config_command} activate {self.conda_env_name}" 

You are welcome to make the PR.