feat(vscode): resolve config by file path

[QiroNT]

What have changed

• The VSCode extension now can load multiple config files according to file's path.
  • Config files will be searched from file's directory to the workspace directory or what's being specified in unocss.root.
  • Every config file will only be loaded once, every file will be searched against loaded configs first.
  • The config file living in CWD will be loaded upon extension start.

Unsolved problems

• Files meeting code.includes(INCLUDE_COMMENT_IDE) || isCssId(id) will now be resolved to default config. Should it use the "closest" config or the default one?
• Should the config file search all the way to the root of the drive? Should it be CWD instead?
• Should there be a command to unload all loaded contexts(aka. reload)? It definitely helps with potential loading issues (eg. when a new config file is added), but I'm not sure if it's necessary.
• Reduce the number of createContext calls. Currently it's being called every time a resolve from cache fails, and it does lot's of disk reads which is slow. I think it could be reduced by a better cache algorithm, haven't came up with one yet.

[netlify]

✅ Deploy Preview for unocss ready!

Name	Link
🔨 Latest commit	34bfd80
🔍 Latest deploy log	https://app.netlify.com/sites/unocss/deploys/62a8b4932f3b8b00093c539c
😎 Deploy Preview	https://deploy-preview-1101--unocss.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[antfu]

For sure we could have a Reload UnoCSS command.