[Bug]: Switch from artifacts to cache for test:conda-build job's generated objects to be used across pipelines

[Syakyr]

Problem Domain

• Gitlab

OS/Platform(s) Used

• None

Problem Brief

Currently the test:conda-build section only saves the conda environment as artifacts, which only saves within the same pipeline. But the environment doesn't need to change unless the conda yaml file changes as well. Thus, we will test whether using cache instead of artifacts would be better suited to store the environment so that we don't have to rebuild the environment every pipeline.

Steps to Reproduce

CI/CD pipeline being triggered upon push of modified files

Expected Result

No need test-conda to run if conda yml file is unmodified.

Actual Result

test-conda has to run otherwise pylint-pytest job will fail.