Cull VS-Code pods after specified time

[Cecilsingh]

This is in addition to the issue mentioned below:
https://github.com/rstudio/rstudio-pro/issues/2044

A customer has requested that once this has been implemented, that there is a way to delete vs-code session containers without killing the main Workbench containers. There are scripts that can be used which perform this, however, it would do so for all containers (PV and Workbench containers). Ideally, this would only ensure that vs-code jobs are killed, not the replicasets. This should also work if there is a restart policy in place

[MariaSemple]

Hey Cecil, thanks for filing this. It's now possible to configure VS Code (and Positron!) session to timeout after a certain period of inactivity.

Admin Guide docs: https://docs.posit.co/ide/server-pro/admin/vscode_sessions/configuration.html
User Guide docs: https://docs.posit.co/ide/server-pro/user/vs-code/guide/session-timeout.html

We do think this could be improved in a couple of ways:

• documentation improvements in this repo
• a better way to configure these values in our Helm Charts
• potentially enable timeouts for both VS Code and Positron session by default

We're going to open issues for the first two above, and have some more conversation internally around the 3rd bullet point. Once issues are created for the others, I will update this issue with links.