[GX-17918] Refactor resolve

[kinetifex]

Summary

This is a refactor to @gasket/resolve necessary for consistent resolve patterns in cli, engine, presets, and metadata-plugin. This PR includes several fixes and changes.

I will highlight the improved separation of concerns changes next.

Changelog

Engine does not implement configured plugin loading

• Problem: What plugins and how they were loaded was not available for uses outside the engine. For example metadata-plugin was accessing private member ._plugin of the engine, which was only a snapshot of useful info gathered by resolve.
• Fix: Loading responsibility of @gasket/resolve which allows non-engine uses.

Engine does not initiate metadata

• Problem: Updates to metadata require changes in two packages, plugin-engine and metadata-plugin. This results in a strange unnecessary relationship where the metadata-plugin would require a specific version of the engine.
• Fix: All metadata definition responsibility of @gasket/metadata-plugin.

Presets do not resolve their own plugins

• Problem: Because presets depend directly on @gasket/resolve, major changes to this package which would be used by the engine and cli would enter a broken state.
• Fix: Now a responsibility of @gasket/resolve, used by the engine and cli.
  • Presets merely define plugins in package.json, and can now define additional data. See [major] basic preset for NextJS #65 for an example.

Engine and metadata-plugin do not resolve package paths

• Problem: Inconsistent plugin and package.json path resolves were occurring due to how resolve being done between these 3 packages, especially when using npm link or --preset-path with the cli.
• Fix: Now solely a responsibility of @gasket/resolve

Test Plan

With the refactor, I was able to write more granular unit tests.

[indexzero]

👍 two most important features to preserve.

[indexzero]

Reviewed the guts of @gasket/resolve (but not the upstream changes). The new separation of concerns feels a lot cleaner. I'm 👍 with a review from @DullReferenceException and/or another person with deep knowledge of @gasket/plugin-engine

[SivanMehta]

Why do you need an empty echo here?