[Feature request] Configure Auto-Save to CloudShell in User Settings

Today when I change things in the workspace, CloudShell doesn't get updated unless do an explicit push. I would like to have an implicit push to CloudShell controlled by a user setting (presuming they use CloudShell as the primary terminal as well).

The issue does not identify files, tests, or entry points. Begin by locating the existing explicit push-to-CloudShell flow and the extension's User Settings registration, then determine how an auto-save setting should trigger that flow. Done means workspace changes are implicitly pushed when enabled and unchanged behavior remains when it is disabled.

Written by the indexing model from the issue text.