Provide guidance to Reflective for VSCode

[jmunroe]

Context

Following on from

• [Support] Reflective Pangeo environment updates #6831

FD ticket: https://2i2c.freshdesk.com/a/tickets/4433

What we need to do

1. Transfer the bnext.bio image to their GitHub Repo
2. Provide guidance on how they can enable a vscode-like interface (likely by pointing the STRUDEL image as an example)
3. Add documentation to the Infrastructure and/or community documentation repositories so that we can self-serve this in future.

Definition of Done

• The feature/service is technically complete
• The feature/service been tested with one or more users (if applicable)
• The feature/service been deployed to a production cluster
• The feature/service has been shown to be replicably deployable
• The feature/service follows our definition of minimally documented
• The feature/service has been added to our product menu (if applicable).
• Lessons learned have been documented
• The feature's availability has been communicated to Sales
• The feature has been communicated to our communities

[jmunroe]

I tried emailing Reflective to continue migration of the image repo to their GH org but hit a permission issue. I've a proposed an alternate plan to the community representatives.

I pulling this issue as a whole back to Up Next -- I don't have capacity to get it do completion in this iteration.

[jmunroe]

The maintenance of their own image appears to be solved ( They are using image: quay.io/nucleus/nucleus-hub:2i2c which is not owned by 2i2c)

I am not sure of the status of vscode integration. This may still be an outstanding support issue we need to address.

[jmunroe]

I've unassigned myself from this particular one because I like help from one of the infra engineers to ensure we are setting it up correctly.

But I also want to use this particular issue to understand better what exactly 'community enablement' is understood by our team.