feat!: move to file-services/resolve as default resolver

[barak007]

This PR replaces enhanced-resolve default resolver with @file-services/resolve which is much faster and easier to use.

Notes:

• This is a breaking change
• The old resolver created by createDefaultResolver is now available from the @stylable/webpack-plugin package and also used by default in it
• Need to migration guide:
  • minimal explanation on the difference between the options of the old and new resolver with an emphasis on alias.
  • removal of resolveOptions

[idoros]

This looks promising, but I've noticed a few issues that I've commented on. Additionally, there's one more thing that I think should be tested:

The Webpack-Plugin currently conducts tests solely with its own resolver. Could you please include a test to ensure that the new default resolver can be integrated and functions correctly? I believe it's essential to guide users in this direction, especially if they have a setup involving multiple integrations and need the resolver to operate consistently across all of them.

Let's review it one more time to ensure that we haven't overlooked anything.