feat: unocss module

[Timeraa]

This PR should make the use of unocss with WXT a fair share easier, see reference issues: #522 #1026
Makes the need for this obsolete: #596

@aklinker1 Any way we can have the vite:devServer:extendConfig have entrypoints as well because then I can get rid of the "Entry module not found." warning you will get when it runs over entrypoints you don't want to use.

Also I am a bit uncertain but I think that unocss.entrypoints should be required so that you don't run it on files where it's not used, what's your opinion?

[netlify]

✅ Deploy Preview for creative-fairy-df92c4 ready!

Name	Link
🔨 Latest commit	f5a1cb6
🔍 Latest deploy log	https://app.netlify.com/sites/creative-fairy-df92c4/deploys/6713ee15f367500008178f1f
😎 Deploy Preview	https://deploy-preview-1043--creative-fairy-df92c4.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 configuration.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.13%. Comparing base (842c158) to head (f5a1cb6).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1043      +/-   ##
==========================================
+ Coverage   82.07%   82.13%   +0.06%     
==========================================
  Files         127      127              
  Lines        6661     6661              
  Branches     1112     1112              
==========================================
+ Hits         5467     5471       +4     
+ Misses       1180     1176       -4     
  Partials       14       14              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[aklinker1]

@Timeraa I made some changes to simplify things:

1. Convert entrypoints to excludeEntrypoints and use entrypoint names instead of paths
2. Add configOrPath option to customize the vite plugin
3. Added plugin to demo extension for testing.

Any way we can have the vite:devServer:extendConfig have entrypoints as well because then I can get rid of the "Entry module not found." warning you will get when it runs over entrypoints you don't want to use.

There isn't unfortunately :/. I see the warning you're talking about, don't know how to remove it.

Also I am a bit uncertain but I think that unocss.entrypoints should be required so that you don't run it on files where it's not used, what's your opinion?

I think leaving it as optional is fine. I added a default of ["background"] for it, so at least the background will be automatically removed. The majority of the time, people will use unocss in most entrypoints. The main reason to add a CSS framework is because you've got lots of CSS, and you want to use it. So I'm not too concerned about that. Someone will create an issue, we'll point them to the line in the docs about it, and everyone else will see that as well.

I have plans to clean up Vite's logs in general, after that it should be possible to improve the warning message and tell them to add the entrypoint to excludedEntrypoints.

[aklinker1]

Ignore the failing Continuous Publish / build check, that happens for new packages.

[Timeraa]

Everything looks fine to me!