lpcraft conda build plugin should install and run conda-build outside of a conda environment

[Dan Ryan]

Currently the conda-build plugin creates a conda environment and installs conda-build, python, etc into that environment, activates it, and performs a build. Conda-build itself then creates additional environments in order to perform the build.

For some packages, however, it appears that during the test phase, the initial conda environment is escaped. The packages search for `conda-inspect`, which is provided by conda-build, in order to inspect build artifact linkages, but cannot find this command as it is only installed in the environment.

In order to solve this I propose changing the default behavior of the conda-build plugin to not create an initial environment in the first place, as it does not encapsulate the build anyway. Instead of running `conda create...` we would just run `conda install ...`

[Jürgen Gmach (jugmac00)]

Sounds reasonable.

I am almost EOW (public holiday), so a MP is welcome. Otherwise I will create one next week, but let you review, as you actually use the plugin.