test: Avoid test failures from unlocking undefined stores

With the previous mock, the entire `@wordpress/data` module was
replaced. This led to emptying utilities like `createReduxStore`. This
resulted in other `@wordpress` modules throwing errors when attempting
to act upon stores.

```
 FAIL  src/utils/editor.test.jsx [ src/utils/editor.test.jsx ]
Error: Cannot unlock an undefined object.
 ❯ unlock node_modules/@wordpress/private-apis/src/implementation.ts:186:9
 ❯ node_modules/@wordpress/blocks/src/store/index.js:31:1
 ❯ node_modules/@wordpress/blocks/src/index.js:11:1
```

Author: dcalhoun

src/utils/editor.test.jsx

@@ -16,7 +16,13 @@ import { unregisterDisallowedBlocks } from './blocks';
 vi.mock( '@wordpress/editor', () => ( {
 	store: { name: 'core/editor' },
 } ) );
-vi.mock( '@wordpress/data' );
+vi.mock( import( '@wordpress/data' ), async ( importOriginal ) => {
+	const actual = await importOriginal();
+	return {
+		...actual,
+		dispatch: vi.fn(),
+	};
+} );
 vi.mock( '@wordpress/preferences' );
 vi.mock( '@wordpress/block-library' );
 vi.mock( './blocks' );