Resolve action deprecation warnings

[dbast]

Current warnings are:

• Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: conda-incubator/setup-miniconda, svenstaro/upload-release-action
• The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The warnings are caused by conda-incubator/setup-miniconda/svenstaro/upload-release-action and have proposed fixes:

• https://github.com/conda-incubator/setup-miniconda/pull/249
• https://github.com/conda-incubator/setup-miniconda/pull/252
• https://github.com/svenstaro/upload-release-action/pull/83

While the proposed fixes are fine, the warnings caused by conda-incubator/setup-miniconda can be avoided by using the Github runner pre-installed miniconda, which also saves some seconds for each action run (see also https://github.com/actions/runner-images/search?q=miniconda where the runners are defined)

[xhochy]

I would also prefer to keep setup-miniconda here as we are actually in a miniconda repo. If performance is an issue, we should be using mamba in the action or switch to provision-with-micromamba.

[dbast]

Well, personal preferences... the action anyways installs nothing in the bundled situation https://github.com/conda-incubator/setup-miniconda/blob/main/src/installer/bundled-miniconda.ts so wouldn't be required at all if the bundled installation is activated directly as done here.

Closing as fixing the setup-miniconda action will resolve it.

[jakirkham]

Updating the setup-miniconda in PR ( https://github.com/conda-forge/miniforge/pull/383 )