Bug: Add key to interface and translation to culture files stops after key

[brandongregoryscott]

Issue
Using the combined command for adding a key to the interface and translation to culture files, the process stops after adding the key. After doing some light debugging, it looks like an error is being thrown and logged out to kazoo_log.txt:

[2021-06-17T08:56:23.847] [ERROR] kazoo - [addKeyAndTranslation]: Canceled: Canceled
    at Object.s [as canceled] (c:\Users\bscot\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:5:1157)
    at h._remoteCall (c:\Users\bscot\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:88:12871)
    at Proxy.b.<computed>.S.charCodeAt.b.<computed> (c:\Users\bscot\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:88:9394)
    at A.showMessage (c:\Users\bscot\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:84:199065)
    at Object.showErrorMessage (c:\Users\bscot\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:93:29270)
    at Object.error (c:\Users\bscot\.vscode\extensions\brandongregoryscott.kazoo-0.2.0\dist\extension.js:187451:27)
    at Object.catch (c:\Users\bscot\.vscode\extensions\brandongregoryscott.kazoo-0.2.0\dist\extension.js:187481:23)
    at addKeyToInterface (c:\Users\bscot\.vscode\extensions\brandongregoryscott.kazoo-0.2.0\dist\extension.js:187760:33)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at addKeyAndTranslation (c:\Users\bscot\.vscode\extensions\brandongregoryscott.kazoo-0.2.0\dist\extension.js:187855:12)
    at _executeContributedCommand (c:\Users\bscot\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:84:108086) {
  vslsStack: [
    CallSite {}, CallSite {},
    CallSite {}, CallSite {},
    CallSite {}, CallSite {},
    CallSite {}, CallSite {},
    CallSite {}, CallSite {},
    CallSite {}, CallSite {}
  ]
}

May be related to microsoft/vscode#69335, since this issue seems to have cropped up since logging was added in 0.1.3 which accesses the workspaceFolders array.

On a related note, it looks like the logging isn't flushed until the extension host is manually restarted... which is not helpful, either.

Workaround
This issue does not exist in version 0.1.2 and earlier.