Add CI to Evaluate Conda ENV setup issues

[dyt811]

Checklist

GitHub

• I've given this PR a concise, self-descriptive, and meaningful title
• I've linked relevant issues in the PR body
• I've applied the relevant labels to this PR
• I've assigned a reviewer

PR contents

• I've consulted ivadomed's internal developer documentation to ensure my contribution is in line with any relevant design decisions
• I've added relevant tests for my contribution
• I've updated the relevant documentation for my changes, including argparse descriptions, docstrings, and ReadTheDocs tutorial pages

Description

Currently even though we offer a conda environment.yml file, it has not been undergoing the same rigorous CI validations as the requirements.txt. Sporadic reports of HOURS long resolving conda environment suggests there are potential issues unidentified. The goal of this PR is to add CI integration to allow us to manually validate the performance latest master branch on conda resolution time. It is not meant to be run automatically or at ever PR.

Linked issues

[coveralls]

Pull Request Test Coverage Report for Build 1022940133

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 70.295%

---

Totals
Change from base Build 1020020617:	0%
Covered Lines:	4120
Relevant Lines:	5861

---

💛 - Coveralls

[dyt811]

On hold for now as VENV/Virtual env approach are heavily favored in open Canada environment instead.