Add additional info to the Quotas page

[lhelms2]

From TMG (Dan):

is there a place in the Delta docs about quotas and how to recover from going over them, resulting in the user getting locked out? lately I see that commonly they’re using VSCode and due to its needing to write to ~/ on login it fails, and users don’t know to do - let alone how to - ssh by terminal to get in and start deleting files to free up their space. I’ve noticed this happening a good deal lately - maybe not more than normal, but even minimizing it by documentation (assuming the user will read them) could be a good thing. if there is a page, TMG can include that in responses to users going forward.

From Greg:

This will be an issue for anyone using vs code and the home directory is Harbor. Lustre was a little forgiving but even then it could happen as well.
I did a quick check but didn’t see this particular suggestion documented ….
I think we can use https://jira.ncsa.illinois.edu/browse/SUP-7346 (peter handled this one)

[lhelms2]

Working in 'quota-vscode' branch.

Have decided to create a 'vs code troubleshooting' page and add this info there instead of adding it to the 'quotas' page (I've cross-linked each page to the other in case a user ends up on either of them).

[lhelms2]

Switched to the 'vscode-troubleshoot' branch.
PR #102

[lhelms2]

Request has evolved into a broader 'VS Code on NCSA Systems' page. From Greg in Slack:

Could you change the title to VS Code on NCSA Resources
and then add pointers to each systems vs code discussion.
and then add a section about “Use Policy” that says things like “do not run large processing work on login nodes.” avoid running vs code plugins that run continually …. etc

Also something about auto-reconnect …

I'm going to do a search in Jira for tickets that talk about a plugin that runs the whole time (auto-reconnect issue).

[pmenstrom]

I need to check with Weddie about how to run VS Code on campus cluster.

[lhelms2]

Under review in PR #102