Set file readonly if class is deployed or if server-side source control reports it not editable

[gjsjohnmurray]

This PR closes #1397

In some circumstances the current VS Code (1.91.1) doesn't correctly switch an editor to be readonly. My PR microsoft/vscode#221023 will resolve this. Meanwhile I am creating this PR as a Draft.

[gjsjohnmurray]

Set as ready so a testable VSIX gets built.

[isc-bsaviano]

Thanks for making those changes

[isc-bsaviano]

Should I wait until that linked Pull Request is merged before I test/approve this?

[gjsjohnmurray]

The issue the linked PR fixes is only likely to affect how this new feature behaves with Deltanji's server-side source control class, because of how when we cancel a checkout we reset the mtime of the document to that of the reinstated version.

Please go ahead and review it.

[isc-bsaviano]

@gjsjohnmurray I installed the dev VSIX and it appears to work as designed. However, the new setting is showing up as an "unknown configuration setting" in the JSON and doesn't appear in the UI. The setting is respected if it's manually added to the JSON though. Also, you don't need to add the explicit default values for the boolean settings within objectscript.export because the parent object has a default configured:

vscode-objectscript/package.json

Lines 1334 to 1347 in c426c7a

	"default": {
	"folder": "src",
	"addCategory": false,
	"map": {},
	"atelier": true,
	"generated": false,
	"filter": "",
	"exactFilter": "",
	"category": "*",
	"noStorage": false,
	"dontExportIfNoChanges": false,
	"maxConcurrentConnections": 0,
	"mapped": true
	},

[gjsjohnmurray]

I pushed a change to remove those defaults.

As for the settings problem, I haven't been able to reproduce this. The setting displays for me in Settings Editor, and when present in JSON it's not marked / tipped as having a problem.

[isc-bsaviano]

@gjsjohnmurray I installed the latest dev vsix and everything looks good. Thanks for this PR!