Publish the next images from the dedicated branch

[azatsarynnyy]

Publish the next images from the dedicated branch that points to a previous commit. It's because the current state of the main branch requires some adaptation to the upstream changes.
This PR allows us to get che-incubator/che-code/insiders with a working terminal until we investigate and fix the eclipse-che/che#21537

[nickboldt]

on a related note, is there a stable branch from which to productize che-code into ds-code?

Right now I only see main and some topic branches at https://github.com/che-incubator/che-code/branches

for DS 3.2 we will NEED a stable branch, be it "7.52.x" or "devspaces-3.2-rhel-8" or some other convention you prefer.

[github-actions]

Pull Request images published ✨
image: quay.io/che-incubator-pull-requests/che-code:pr-69-amd64
Dev image: quay.io/che-incubator-pull-requests/che-code-dev:pr-69-dev-amd64

[github-actions]

Pull Request images published ✨
image: quay.io/che-incubator-pull-requests/che-code:pr-69-amd64
Dev image: quay.io/che-incubator-pull-requests/che-code-dev:pr-69-dev-amd64

[azatsarynnyy]

on a related note, is there a stable branch from which to productize che-code into ds-code?

@nickboldt I've created https://github.com/che-incubator/che-code/tree/devspaces-3.2-rhel-8

[github-actions]

Pull Request images published ✨
image: quay.io/che-incubator-pull-requests/che-code:pr-69-amd64
Dev image: quay.io/che-incubator-pull-requests/che-code-dev:pr-69-dev-amd64

[github-actions]

Pull Request images published ✨
image: quay.io/che-incubator-pull-requests/che-code:pr-69-amd64
Dev image: quay.io/che-incubator-pull-requests/che-code-dev:pr-69-dev-amd64