Document issues around auto-termination of orphaned workspaces

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Work on this issue
• Close this issue

MR: Pending

Description

Update Remote Development user documentation with caveats around behavior of auto-termination of orphaned workspaces, as described in &11452 (comment 1559480059):

We need to be aware of the implications of this approach:

1. The user experience isn't great. If we leave all the associations to CASCADE DELETE, when the associated records are deleted, the workspace record disappears immediately from the database, UI, and everywhere.
2. This means the experience will be that the user doesn't see the workspace in the UI anymore, but the workspace will still be running and accessible for some period of time, maybe not until the next full reconcile which may be for several minutes.
3. This could be a confusing experience, so we will need to be sure to document this behavior.

The docs should not be merged until the implementation is complete: Orphaned workspaces should be auto-terminated (#425248)

Acceptance Criteria

• Docs are updated to clearly describe this behavior, the scenarios in which it can occur, and set expectations