[ENH] - Allow arbitrary configuration files for local and cloud integration tests

[marcelovilla]

Feature description

We currently have an action to initialize Nebari with some predefined configuration parameters. That is the config that we're using for our local integration tests. For our cloud tests (i.e., AWS, Azure and GCP), we rely on pytest fixtures to create a predefined config file.

It would be incredible useful if developers could trigger any of these tests with an arbitrary set of config options or nebari-config.yaml file.

Value and/or benefit

As developers, we're constantly deploying Nebari to make sure new features, bug fixes, and releases work as expected. Sometimes, this includes deploying Nebari with specific configuration options and not the default ones we have on our tests. I believe we can improve the development experience and get more confidence if we allow developers to trigger our integration tests with specific config options.

Anything else?

No response