fix: Ensure hook registration occurs in global wp.hooks namespace

Localizing the `@wordpress/hook` package meant two namespaces existed:

1. The localized module bundled by Vite;
2. And the `wp.hooks` global provided by the remote site scripts.

Hooks registered by GutenbergKit used the former, but the latter is the
namespace utilized by the running editor. Therefore, the hooks were
never applied.

The localization of `@wordpress/hooks` was originally done in service of
our top-level usage of the `@wordpress/api-fetch` module for fetching
remote assets. Localizing dependencies like this may be misguided and
have no impact on the outcome at all, as Vite configuration does not
impact `node_modules`, only GutenbergKit source.

Additionally, we likely have opportunity to refactor and remove our
localization of the `@wordpress/api-fetch` module entirely. We now fetch
editor assets via the native code. We no longer needs to load the
`apiFetch` utility before the remote sites scripts are loaded.

Author: dcalhoun

vite.config.remote.js

@@ -38,7 +38,7 @@ function externalize( id ) {
 	return (
 		!! externalDefinition &&
 		! id.match( /\.css(?:\?inline)?$/ ) &&
-		! [ 'apiFetch', 'i18n', 'url', 'hooks' ].includes(
+		! [ 'apiFetch', 'i18n', 'url' ].includes(
 			externalDefinition[ externalDefinition.length - 1 ]
 		)
 	);
@@ -67,8 +67,8 @@ function wordPressExternals() {
 
 				if (
 					! externalDefinition ||
-					/@wordpress\/(api-fetch|url|hooks)/.test( id ) ||
-					/@wordpress\/(api-fetch|url|hooks)/.test( module )
+					/@wordpress\/(api-fetch|url)/.test( id ) ||
+					/@wordpress\/(api-fetch|url)/.test( module )
 				) {
 					continue; // Exclude the module from externalization
 				}