WIP: Adds ability to set alternate local folder for config/metadata directory

[cfleur]

WIP!

Closes #108

Based on v1.3.2 due to problems running retrievals on v1.4.0 (see #107).

Config directory is specified in config_setup.yml.

Includes cherry pick of Use sys.executable instead of .venv/bin/python to run retrievals

[netlify]

✅ Deploy Preview for em27-retrieval-pipeline ready!

Name	Link
🔨 Latest commit	5db6172
🔍 Latest deploy log	https://app.netlify.com/sites/em27-retrieval-pipeline/deploys/66fff7bf8ca39000089eb23e
😎 Deploy Preview	https://deploy-preview-109--em27-retrieval-pipeline.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[cfleur]

@dostuffthatmatters do you have any comments on this?
TODO: clean up repeated code, maybe something else

[dostuffthatmatters]

This is a great idea! Thank you.

We actually just started a second metadata repository because one of our measurement campaigns produced so much metadata.

I would prefer if one passes the alternative config directory via the command line instead of a separate config_setup.yaml file.

What do you think?

[cfleur]

@dostuffthatmatters I tested the fix for pressure null values #107 and its working. I will rebase this to the latest updates.
Regarding specifying the location for the folder. I thought about this and think it would be nice to have this set as an environment variable. I think the command line arguments can get a little messy. Especially depending how one is calling the pipeline, it might get long. What do you think? Then the user can set the environment variable however they want.

[dostuffthatmatters]

@cfleur great that it works now!

Agreed. Command line arguments might be messy because you also have to add it to every single CLI command/call. Environment variables is a good way of doing it.

[cfleur]

Closing as PR #111 opened instead from different branch.