Today we use che-code main branch to build devspaces/code_3.x.

But for the 3.1 stable branch, we need an upstream tag or branch, like we have with theia and idea.

Once branch or tag is in place, we need either:

• automation to generate new tags/branches every 3 weeks with every Che release, or
• agreement to do a manual update when needed on an adhoc basis

If the former, we can update https://github.com/redhat-developer/devspaces/blob/devspaces-3-rhel-8/product/updateVersionAndRegistryTags.sh to use the appropriate tag/branch in job-config.json

If the latter, then need to manually keep job-config.json updated.