Refs: #51585

• any os @misolori
• any os @JacksonKearl

Complexity: 4

Have an extension that contributes a FileSystemProvider which when registered specifies isReadonly: true.
If you do not want to write a new FileSystemProvider simply take an already existing extension and modify their FileSystemProviders to be readonly. Example extensions: remote hub, mem fs.

Open vscode, have your extension active and try to modify the file system inside vscode - this should not be possible. All commands / actions that modify resources should be disabled or should throw an error when being executed. Here is a list of commands which should be checked:

• Explorer title actions
• Explorer context menu actions
• Explorer actions which can be triggered via keybinding (rename, delete)
• Command pallete actions (example: new file, new folder)

Also verify the editor opens in readonly mode and no modification is allowed in the editor.