[Docs] Better dev environment for coffea-casa

[oshadura]

Watching the efforts of @mat-adamec @zorache to write and commit a code from coffea-casa, I realized we need to add in documentation good practices for easier development (e.g. vscode+jupyterhub: https://blog.jupyter.org/connect-to-a-jupyterhub-from-visual-studio-code-ed7ed3a31bcb)

cc: @bbockelm @kenbloom

[mat-adamec]

This is an old issue, so I think I've lost some of its context. Does this just mean good practices for organizing files on coffea-casa? In that case, I feel like this should be covered by the Git section, since everything on coffea-casa runs through Git.

[oshadura]

It will be nice to show how to develop locally on Visual Studio while connected to coffea-casa Jupyterhub. @alexander-held tried this feature I think, and maybe could give us feedback if it could be useful to have it as part of docs?

[alexander-held]

I wanted to try this out but have not done it so far. I think some users may prefer working with their local customized vscode, and showing how exactly to set it up (not sure whether there exist potential pitfalls, I have not tried this with coffea-casa) would be useful.

[maxgalli]

@oshadura it looks like there was already an issue for what we just discussed, so I will write down the summary here.
I tried to connect to the jupyter hub from Cursor following essentially what is written here.
The notebook succeeds in running the code on the remote server, but then I could not find a way to access locally the list of remote files and/or create new files remotely from the local interface, effectively making the usage of Cursor impossible.
Maybe it would be possible to add VSCode or something similar to the list of items that can be run remotely? This way it would be used via the browser.