Fix for activating environment and installing packages properly

[rajeee]

This fixes the ongoing issue where the environment is not properly created in eagle.

Pull Request Description

For some reason, if you run "module load conda" when an environment is already activated, the environment silently gets deactivated. And it can't be activated again by "source activate <path_to_env>" unless it is deactivated explicitly fist.

Evidence:

<log in to eagle>
[radhikar@el3 ~]$ which python
/nopt/nrel/apps/anaconda/mini_py37_4.8.3/bin/python
[radhikar@el3 ~]$ source activate /shared-projects/buildstock/envs/test_env6
(test_env6) [radhikar@el3 ~]$ which python
/shared-projects/buildstock/envs/test_env6/bin/python
<environment is activated>
(test_env6) [radhikar@el3 ~]$ module load conda
(test_env6) [radhikar@el3 ~]$ which python 
/nopt/nrel/apps/anaconda/mini_py37_4.8.3/bin/python
<environment got silently deactivated>
(test_env6) [radhikar@el3 ~]$ source activate /shared-projects/buildstock/envs/test_env6
(test_env6) [radhikar@el3 ~]$ which python
/nopt/nrel/apps/anaconda/mini_py37_4.8.3/bin/python
 <environment failed to get activated again>
(test_env6) [radhikar@el3 ~]$ source activate /shared-projects/buildstock/envs/test_env6
(test_env6) [radhikar@el3 ~]$ which python 
/nopt/nrel/apps/anaconda/mini_py37_4.8.3/bin/python
<environment failed to get activated again>
(test_env6) [radhikar@el3 ~]$ source deactivate
DeprecationWarning: 'source deactivate' is deprecated. Use 'conda deactivate'.
[radhikar@el3 ~]$ source activate /shared-projects/buildstock/envs/test_env6
(test_env6) [radhikar@el3 ~]$ which python
/shared-projects/buildstock/envs/test_env6/bin/python
<environment can be activated again after explicit deactivation>

Checklist

Not all may apply

• Code changes (must work)
• Tests exercising your feature/bug fix (check coverage report on CircleCI build -> Artifacts)
• All other unit tests passing
• Update validation for project config yaml file changes
• Update existing documentation
• Run a small batch run to make sure it all works (local is fine, unless an Eagle specific feature)
• Add to the changelog_dev.rst file and propose migration text in the pull request

[nmerket]

This looks great. Thank you for figuring this out! Can you add something to changelog_dev.rst?

[nmerket]

Looks good to me. I'll port this over to make a 0.19.2 version as well. Of course we're in the middle of system time right now.