Test: (simple) Notebook file working copy

[bpasero]

Refs: #117873

• macOS @misolori
• linux @connor4312
• windows @dbaeumer

Complexity: 3

Create Issue

---

Install the ms-vscode.vscode-github-issue-notebooks extension and run your test on issue notebooks. You can use the ones we have in .vscode/notebooks

Test:

• dirty notebooks restore properly with the unsaved changes after restarts
• dirty notebooks restore properly when you run code-insiders <path to folder> <path to file in folder> provided the folder you point to has dirty notebooks in it (this way of launching is special because we do not restore the previous editors and only open the ones from the command line + any editor with backup)
• you can save/revert the notebook (be creative and try to break that statement, e.g. by repeated rapid saving operations)
• notebooks (only if not dirty) update when file changes externally
• make a notebook dirty and save the file externally with some changes and verify that you get a save error for preventing dirty writes and you are offered actions to resolve the conflict
• you can open a notebook and a text editor side by side (currently not supported in same group) and both editors have individual dirty contents that restore properly after restarts

//cc @jrieken