Conda 24 caused an issue with json output for environments with
pip packages in the environment file.

This also downgrades Mamba to 1.5.5 but upgrades python to 3.10.13.

conda_version: 24.1.2
conda_mamba_version: 1.5.7

JIRA INFRA-9397

Added Ubuntu 20 and 22 compatibility

See merge request !7

JIRA INFRA-6368

Skipping the 'else' statement seems to work in Molecule, and even
when running ansible-playbook from the local Molecule environment.
However, on AWX this fails with 'the inline if-expression on line 1
evaluated to false and no else section was defined'.

Add Mamba to Conda installation and use Mamba by default

See merge request !6

JIRA INFRA-6207

Add ESS Linux support to role

See merge request !4

ICSHWI-7320

ICSHWI-7320

Custom Dockerfile.j2 template required for ESS Linux,
as package names differ from that used by the default
template shipped with Molecule.

ICSHWI-7320

[ICSHWI-7320]

JIRA INFRA-2513 #action In Progress

ics-conda-forge should be used instead

JIRA INFRA-2156 #action In Progress

JIRA INFRA-2148

JIRA INFRA-1563

JIRA INFRA-1563 #action In Progress

By default, we have:
default_channels:
  - https://repo.anaconda.com/pkgs/main
  - https://repo.anaconda.com/pkgs/r

Set it to an empty list to make sure repo.anaconda.com
is not accessed (there shouldn't be any connection to it from the TN).

JIRA INFRA-1560 #action In Progress

Using the conda_env module is more robust.
- If the handler failed for any reason, the env file had to be deleted
  for it to run again
- conda_env ensures the environment is up to date without having to recreate it

Using the conda module to update conda prevents to update from version
older than 4.6 (the module requires 4.6).
Using the command module should allow to update from older versions.