Pass current namespace to argo via environment variable

[krassowski]

Reference Issues or PRs

• Closes [BUG] - Scheduler does not work when argo workflows are disabled #2256 (it turned out to be an issue with hardcoded namespace in argo-scheduler)
• Requires Allow to specify conda store service namespace via environment variable argo-jupyter-scheduler#7 (and new release of argo-jupyter-scheduler) to take effect
• See Hard-coded namespace breaks scheduler when nebari deployment uses namespace different from dev argo-jupyter-scheduler#6 for context

What does this implement/fix?

Put a x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features not to work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

• Did you test the pull request locally?
• Did you add new tests?

Any other comments?

[viniciusdc]

Hi @krassowski this LGTM, I just need to make sure all the vars are defined already and have some defaults. Then we can merge

[viniciusdc]

Tested with GCP, needs a new release of the docker images that contains the released version (see PR) of the argo-jupyter-scheduler , but can be merged.