docs: add instructions for setting Studio version label to custom studio images

[georgi-seqera]

Summary:

Updating instructions for custom studio creation steps to include adding a image label io.seqera.connect.version to identify the connect-client version used based on image label metadata.

Note: This change is not tied to any release as it is purely widely supported Docker functionality and hence can be applied to docs at any time and even can be applied to older enteprise version documentation.

Context:

Certain studio functionalities require the Seqera Platform to know the version of the connect-client used at the point of configuring and launching the studio.

To do this effectively, all custom built studio images must have a io.seqera.connect.version label with the connect-client version used going forward.
While the absence of the label will not block a studio being started (and will work as before), it might not support all new functionalities (e.g. ssh connectivity).

Related updates:

• The custom-studios-examples repository is being updated with the same change to reflect the documentation
  • feat: add connect-client version label to images custom-studios-examples#16
• Additionally we'd perhaps want to update blog post for custom studios to also reflect this additional step as the blog post is widely referenced and useful
  • https://seqera.io/blog/deploy-custom-apps-studios/

[netlify]

✅ Deploy Preview for seqera-docs ready!

Name	Link
🔨 Latest commit	34498dc
🔍 Latest deploy log	https://app.netlify.com/projects/seqera-docs/deploys/697cff5039c3cb0008b02bbd
😎 Deploy Preview	https://deploy-preview-1068--seqera-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[justinegeffen]

Thanks, @georgi-seqera! This PR is for the Cloud docs only. From what I understand, it'll be best to backport it to all the Enterprise docs?

[georgi-seqera]

From what I understand, it'll be best to backport it to all the Enterprise docs?

Well, actually, if I think about it more, probably not. Needed just for the Enterprise 25.3 docs from which point we'll be using the new label on the studio inside Platform logic.

Reason I was thinking of backporting to all Enterprise docs, is because the extra step is totally backwards compatible and anyone building custom studios based off of older Enterprise docs would have an easier and smoother transition when they upgrade to 25.3 (their studios would just work with no issue, whereas otherwise they'll likely have to rebuild some of them).

But realistically it's not essential and could be misleading even so I retract my idea and we should just add it to relevant 25.3 docs.

[github-actions]

📝 Documentation Review Summary

Check	Status
Voice/Tone	✅ success
Terminology	✅ success

---

Review powered by Claude Code editorial agents

To apply suggestions:

• Click "Commit suggestion" on individual inline comments
• Select multiple suggestions and batch commit them together