Make Tintype VS Code mocks safe for Jest hoisting

Summary:
Wrap the shared VS Code mock functions in lazy forwarding callbacks so Jest 29's hoisted `jest.mock()` factory does not evaluate top-level `const` mocks before initialization. Type the wrapper returns as `unknown` to satisfy strict xplat linting without changing runtime behavior.

___

Differential Revision: D116877448

fbshipit-source-id: 08c2fad9a34771175f4e942f74c49fa3d884df14

Author: pdepetro

vscode/core/src/snapshot/__tests__/snapshot-provider.test.tsx

@@ -39,18 +39,19 @@ jest.mock('vscode', () => ({
     },
   },
   window: {
-    showErrorMessage: mockShowErrorMessage,
-    showInformationMessage: mockShowInformationMessage,
-    showWarningMessage: mockShowWarningMessage,
-    showSaveDialog: mockShowSaveDialog,
+    showErrorMessage: (...args: unknown[]): unknown => mockShowErrorMessage(...args) as unknown,
+    showInformationMessage: (...args: unknown[]): unknown =>
+      mockShowInformationMessage(...args) as unknown,
+    showWarningMessage: (...args: unknown[]): unknown => mockShowWarningMessage(...args) as unknown,
+    showSaveDialog: (...args: unknown[]): unknown => mockShowSaveDialog(...args) as unknown,
   },
   workspace: {
     fs: {
       stat: (uri: unknown): Promise<unknown> => mockFsStat(uri) as Promise<unknown>,
     },
   },
   commands: {
-    executeCommand: mockExecuteCommand,
+    executeCommand: (...args: unknown[]): unknown => mockExecuteCommand(...args) as unknown,
   },
   Uri: {
     file: (fsPath: string) => ({fsPath, path: fsPath, scheme: 'file'}),