feat(kit): support followSymbolicLinks option for resolveFiles

[Diizzayy]

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This PR allows module authors to opt-out of following symbolic links when using resolveFiles, as there are many cases where this current default isn't the desired.

[netlify]

✅ Deploy Preview for nuxt3-docs canceled.

Name	Link
🔨 Latest commit	2a6f905
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/62e7932876410a000853184c

[pi0]

Can you please make 3rd argument an object { followSymbolicLinks }

[pi0]

Thanks for PR @Diizzayy. In the future, please consider opening an issue describing improvement and enhancement 🙏🏼 Also what is the current use case you have for this utility for skipping link resolution? Knowing context, can help to improve utilities and be aware of usecases.

[Diizzayy]

In the future, please consider opening an issue describing improvement and enhancement 🙏🏼

Sorry about that, I had begun writing an issue when I realized that this was the underlying cause.
I'll be sure to keep this in mind going forward. I jumped the gun here.

Also what is the current use case you have for this utility for skipping link resolution

@pi0 When using pnpm workspaces which uses symlinks between packages, you'll find that based on how the resolveFiles utility is used in a module, it's default behavior ( following symlinks ) can result in scanning deeply nested files in node_modules that match the pattern ( which may not be the desired ). This can also lead to an almost infinite loop of resolving files when a symlinked package depends on another that also contains matching files (which is where I encountered it).