Support option for environment activation

[esloch]

We need to add support for conda environment activation that will activate the environment beforehand before executing the environment.

for now, let's just support conda.

version: 1.0
env-file: .env
virtual-environment:
  application: conda
  name: my-env
groups:
  php:
    targets:
      print:
        help: print 1
        run: |
           print('1')

this option should be defined just in the global scope.
we need to investigate it later if we would like to have it for group and target scope as well.

for now, we don't need to implement source, but it would be nice to have that, so it could create an environment in the case it doesn't exist.

[xmnlab]

before this line https://github.com/osl-incubator/makim/blob/main/src/makim/core.py#L94C1-L107C1

we could have something like this:

        venv = self.global_data.get('virtual-environment'. {})
        venv_app = venv.get({'application', ''})
        venv_name = venv.get({'name', ''})

        self.shell_app(
            *self.shell_args,
            f"{venv_app} activate {venv_name}",
            _in=sys.stdin,
            _out=sys.stdout,
            _err=sys.stderr,
            _bg=False,
            _bg_exc=False,
            _no_err=True,
            _env=os.environ,
            _new_session=False,
        )

[abhijeetSaroha]

        self.shell_app(
            *self.shell_args,
            f"{venv_app} activate {venv_name}",
            _in=sys.stdin,
            _out=sys.stdout,
            _err=sys.stderr,
            _bg=False,
            _bg_exc=False,
            _no_err=True,
            _env=os.environ,
            _new_session=False,
)

It doesn't work, gives no such file or directory error, when try to activate the environment.
I think because that's the the place for filepath not for the shell command.

[xmnlab]

I see . but that is the general idea ... you can try different things there
this is the page for the sh library https://github.com/amoffat/sh
so maybe instead of self.shell_app .. it could be something like (for example)

sh_venv = getattr(sh, venv_app)

sh_venv(
            f"activate {venv_name}",
            _in=sys.stdin,
            _out=sys.stdout,
            _err=sys.stderr,
            _bg=False,
            _bg_exc=False,
            _no_err=True,
            _env=os.environ,
            _new_session=False,
)

but cretes a jupyter notebook and play a bit with that
try to explore different things and approaches

[xmnlab]

this is a bit more complex than we expected ...
maybe for providing that we would need to use some specific backend, for example nox, that supports it ...
maybe we could do something similar, but we would need to investigate it more