fix(runtime-core): improve error messages clarity and fix preload resourceCategory bug

Summary

Reviewed and improved error messages across packages/runtime-core to make failures
easier to diagnose for both developers and AI agents. Also fixed a silent logic bug
in the preload asset generation path.

Bug Fix

plugins/generate-preload-assets.ts: Assignment operator = was used instead of
strict equality === in the resourceCategory branch check. This caused the condition
to always be truthy and silently overwrite preloadConfig.resourceCategory to 'sync'
for every non-'all' entry, resulting in incorrect preload asset selection with no error
reported.

- } else if ((preloadConfig.resourceCategory = 'sync')) {
+ } else if (preloadConfig.resourceCategory === 'sync') {

Error Message Improvements

utils/load.ts

• ESM entry load failure (loadEsmEntry): bare reject(e) in catch now includes the
  entry URL and original error message.
• SystemJS entry load failure (loadSystemJsEntry): same as above.
• Node.js entry load failure (loadEntryNode): bare throw e now includes remote name
  and entry URL.
• All three use error() from logger.ts so the [ Federation Runtime ] prefix is
  applied consistently.

plugins/snapshot/SnapshotHandler.ts

• RUNTIME_007: args previously passed hostName: moduleInfo.name (which is actually
  the remote name) and omitted the actual host. Now correctly passes remoteName,
  remoteVersion, and hostName separately so the error context is unambiguous.
• Manifest structure validation (assert): replaced the generic
  "${url} is not a federation manifest" message with one that names the remote and
  lists exactly which required fields (metaData, exposes, shared) are missing.

shared/index.ts

• loadShare assertion: message now quotes the package name and host name, and provides
  an actionable hint about where to declare the shared config.
• initRemoteModule: when errorLoadRemote hook returns undefined (no plugin handled
  the error), the function now returns early instead of falling into the finally block
  with an undefined remoteEntryExports, which previously caused a silent no-op or
  potential Cannot read properties of undefined crash.

utils/share.ts

• formatShare — missing get/lib error: now includes the package name and source
  module (from) so it's clear which share registration is misconfigured.
• formatShare — eager + treeShaking conflict: now includes the package name and
  source module instead of a generic string.
• Both use error() from logger.ts for consistent prefix handling.

global.ts

• getInfoWithoutType: generic 'key must be string' replaced with the actual type
  and serialised value of the bad argument.

remote/index.ts

• removeRemote: logger.log(...) (info-level) changed to logger.error(...) so the
  failure surfaces at the correct severity level.

Testing

All changes are confined to error paths (catch blocks, assertions, and branch conditions).
The preload bug fix restores the originally intended sync-only asset filtering behavior.