feat(IDX): use tags instead of image id

[cgundy]

Since splitting out into two images ic-dev and ic-build the logic has become quite a bit more complex. Although we use the same tags for both images, they have different image ids:

• https://github.com/dfinity/ic/pkgs/container/ic-build/712860203?tag=7901a473a840d3dcddd8f5b21fd34c9131c75e9f56e3c5617ec579584ceb4b64
• https://github.com/dfinity/ic/pkgs/container/ic-dev/712859056?tag=7901a473a840d3dcddd8f5b21fd34c9131c75e9f56e3c5617ec579584ceb4b64

For this reason, it's easier to update our CI to use image tags instead of image ids when referencing the images.

[github-actions]

Run URL: https://github.com/dfinity/ic/actions/runs/22576409609

New container tag: 7901a473a840d3dcddd8f5b21fd34c9131c75e9f56e3c5617ec579584ceb4b64

[basvandijk]

Nice. Thanks. I'll close #9094.

[nmattia]

out of curiosity, is there a reason we use a tag additionally to the image id? both are a hashed representation of the inputs, though the image ID is guaranteed to be correct, right?

[cgundy]

My understanding is that the image tag is for CI logic - so that we know when to re-trigger a container build. Otherwise we'd need to query the registry.

[basvandijk]

Carly and I also had a chat about whether to go for tags or image IDs. One advantage of image IDs is that it's completely unambiguous which image you're using whereas referencing an image via tag could result in a different image if the image was later rebuild and reuploaded.

[fspreiss]

@cgundy, you closed the PR: is there an alternative PR achieving the same thing: I'm basically waiting for the gh command to be available in the devcontainer in VSCode/Cursor (because my AI agent wants to use it).

[cgundy]

@fspreiss yes, I closed it in favor of this one: #9099