fix: disable app sandbox when --no-sandbox is present

[deepak1556]

Refs #184687

[bpasero]

I would have expected us to simply go strict for --no-sandbox and not introduce a new thing --sandbox to keep the change small and match our expected args.

[deepak1556]

@bpasero it is not possible to rely on the boolean attribute of no-sandbox because of how minimist works, see

vscode/src/vs/platform/environment/node/argv.ts

Lines 170 to 175 in 46041c9

	// Minimist incorrectly parses keys that start with `--no`
	// https://github.com/substack/minimist/blob/aeb3e27dae0412de5c0494e9563a5f10c82cc7a9/index.js#L118-L121
	// If --no-sandbox is passed via cli wrapper it will be treated as --sandbox which is incorrect, we use
	// the alias here to make sure --no-sandbox is always respected.
	// For https://github.com/microsoft/vscode/issues/128279
	'no-sandbox': { type: 'boolean', alias: 'sandbox' },

for reference. We have been aliasing sandbox to no-sandbox, so this PR does not introduce a new flag. It works like this,

code <folder> // sandbox: true, no-sandbox: undefined (from minimist)

code <folder> --no-sandbox // sandbox: false, no-sandbox: false (from minimist)

[bpasero]

Thanks!