Add workflow to run conda-store user journey tests

[soapy1]

Reference Issues or PRs

fixes #2760

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): CI change

[soapy1]

depends on conda-incubator/conda-store#1040

[viniciusdc]

Since these tests depend on a live cluster, I suggest extending the already existing local integration tests with this extra check https://github.com/nebari-dev/nebari/blob/main/.github/workflows/test_local_integration.yaml -- since it uses CiRun under the hood you should not be affected by any flakiness of the GH runner in case of constrained resources.

[aktech]

My 2 cents on this: Iterating on these tests can be painful as it takes 20+ min to get the feedback (assuming deployment succeeded), I have found https://github.com/marketplace/actions/debugging-with-tmate to be quite useful to ssh into the runner and debug failures.