[BUG] - Local integration tests fail after updating the Nebari version constant without a new release of the Docker images

[marcelovilla]

Describe the bug

When preparing a release, the RELEASE_VERSION constant has to be updated to match the new release version of Nebari. This is used to pull the corresponding Docker images for different services, including nebari-workflow-controller. If the image tag is updated but the Nebari Docker images have not been released with that tag, the deployment will fail when trying to pull the images.

Here's an example: https://github.com/nebari-dev/nebari/actions/runs/12952884533/job/36131250412

Expected behavior

Services should pull existing images (e.g. using the main tag), or it should be reflected in our docs that the release process has a
prerequisite of cutting the Docker images first.

OS and architecture in which you are running Nebari

GitHub Actions

How to Reproduce the problem?

Update the RELEASE_VERSION constant to a version where no Nebari Docker images exist yet and let the local integration tests run in GitHub Actions

Command output

Versions and dependencies used.

No response

Compute environment

None

Integrations

No response

Anything else?

If/when we move the Docker images back to this repo, this problem should be alleviated if we make sure to grab the images we're building when running the local integration tests.