Update tools injector image

Issue: Extract tools-injector from gitlab-web-ide-vsco... (#441427 - closed)

What does this MR do and why?

With the version 1.0.0 release of the gitlab-workspaces-tools, we can now replace the tools-injector image to use the one built by the new repo. The reason behind this is to decouple the tools injector from the web-ide-vs-code-fork.

MR acceptance checklist

• Workspaces can be created with the new image with no errors/regression in behaviour

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After
old_tools_image	new_tools_image

How to set up and validate locally

1. Setup GDK
2. Ensure the current GitLab branch is this MR's branch
3. setup remote-development locally and create a workspace

Numbered steps to set up and validate the change are strongly suggested.

added Category:Remote Development devopscreate groupide sectiondev typefeature workflowin dev rd-workflowprioritized labels

assigned to @Saahmed

added pipelinetier-1 label

changed milestone to %17.2

added backend label

	2 Warnings
	a788abb4: The commit subject must start with a capital letter. For more information, take a look at our Commit message guidelines.
	f18048ea: The commit subject must start with a capital letter. For more information, take a look at our Commit message guidelines.

Reviewer roulette

Category	Reviewer	Maintainer
backend	@tyleramos (UTC-4)	@avielle (UTC+2)

Please check reviewer's status!

• Reviewer is available!
• Reviewer is unavailable!

Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

changed title from Draft: update tools injector image to Draft: Update tools injector image

changed the description

mentioned in issue #441427 (closed)

marked the checklist item Workspaces can be created with the new image with no errors/regression in behaviour as completed

Hello! @ealcantara the previous image registry.gitlab.com/gitlab-org/gitlab-web-ide-vscode-fork/web-ide-injector:9 appears to have been using vscode "version": "1.85.2". The updated image uses version 1.89.1-1.0.0-dev-20240612072203 of the fork as explained in the release notes.

Is it safe to bump the version in this MR or is there a release/testing/validation process I would need to complete that I have missed somewhere? LMK your thoughts, thank you!

requested review from @vtak and @ealcantara

marked this merge request as ready

Looking now

mentioned in merge request gitlab-web-ide-vscode-fork!84 (merged)

approved this merge request

@Saahmed - Our docs mention the minimum GLIBC version(2.28) we support for our VS Code fork. So I tested it with an image with has this glibc version and it is working. I verified the pod logs and nothing unusual over there.

LGTM!

@ealcantara - Can you merge this?

added pipeline:mr-approved label

added pipelinetier-2 label and removed pipelinetier-1 label