feat(lib): add m3.less standard library

[WalkQuackBack]

Investigate Google's M3 variables part of #1803

#1705 M3 component

[WalkQuackBack]

Ready to push this through. In my opinion, Google specific shared stuff would be better off separated into another library considering the vast variety of tech stacks used (Wiz+soy, Angular, Next.JS, Flutter, etc).

[uncenter]

Ready to push this through. In my opinion, Google specific shared stuff would be better off separated into another library considering the vast variety of tech stacks used (Wiz+soy, Angular, Next.JS, Flutter, etc).

Can you elaborate? Where else would it be used? What from this lib PR would be split off, what would the new one be called, etc?

[WalkQuackBack]

Ready to push this through. In my opinion, Google specific shared stuff would be better off separated into another library considering the vast variety of tech stacks used (Wiz+soy, Angular, Next.JS, Flutter, etc).

Can you elaborate? Where else would it be used? What from this lib PR would be split off, what would the new one be called, etc?

Sorry, didn't see this! I was thinking seperating out things like the One Google menu that's used in several apps, pictured below:


Secondly, things that are themable using --og- prefix, among other modified OSS libraries such as MDC

Cookie banners, part of the "glue" framework