Fix: Workflow maintaing conda environment

[fmalatino]

Description
This PR ensures that the same shell is opened across workflow steps and no longer calls for removal of sqlite after installation.

🚧
To be merged after PR 146 in Pace

Fixes:
Current issues in the workflow

How Has This Been Tested?
Tested with the current set of unit tests

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules
• New check tests, if applicable, are included
• Targeted model, if this change was triggered by a model need/shortcoming

[bensonr]

I think we need to be careful about specifying bash as its behavior can change as we update the underlying container or system OS.

[jjuyeonkim]

Looks good to me -- similar to NOAA-GFDL/pace#146.

[romanc]

Is this shell specification still necessary?

[fmalatino]

Yes, without it the python installed in the conda environment cannot be accessed.

[romanc]

All other steps seem to be fine with the default run shell specification in lines 29-31. How is this step different?
I guess I'm missing something obvious here ... just asking cause I'm curious how this works.

[fmalatino]

Oh...I totally forgot to remove this, thanks!

[fmalatino]

I think we need to be careful about specifying bash as its behavior can change as we update the underlying container or system OS.

We can add other shells to test when needed, as is depicted in this documentation.