fix(vscode): write mypy settings at ws scope

v0.4.18

applyAllocatorSetting wrote mypy.dmypyExecutable and
mypy.runUsingActiveInterpreter at WorkspaceFolder scope, the
only writes in the module not using Workspace scope. When the
window is opened via a .code-workspace file (where these keys
and cmk.mypy.allocator already live), the folder-scoped update
is rejected, so the reconcile threw and surfaced as "re-apply
failed". The previous weOwn guard masked it by short-circuiting
before the write; removing that guard made the write
unconditional and exposed the failure. Write at Workspace scope
to match the allocator setting and the user's existing values.

CMK-36081

Change-Id: Ib0609b8a1e619263603892f98f6d8f4f2430bca6

Author: otAAAh

.ide/vscode/src/profiles/python/jemallocAllocator.ts

@@ -184,7 +184,7 @@ async function updateDmypyExecutable(
 ): Promise<void> {
   await vscode.workspace
     .getConfiguration('mypy', wsFolder)
-    .update(DMYPY_SETTING, value, vscode.ConfigurationTarget.WorkspaceFolder)
+    .update(DMYPY_SETTING, value, vscode.ConfigurationTarget.Workspace)
 }
 
 async function updateRunUsingInterpreter(
@@ -193,7 +193,7 @@ async function updateRunUsingInterpreter(
 ): Promise<void> {
   await vscode.workspace
     .getConfiguration('mypy', wsFolder)
-    .update(RUN_USING_INTERPRETER_SETTING, value, vscode.ConfigurationTarget.WorkspaceFolder)
+    .update(RUN_USING_INTERPRETER_SETTING, value, vscode.ConfigurationTarget.Workspace)
 }
 
 function openInstallTerminal(install: InstallCommand): void {