Add more built-in colors

[zjijz]

eThis adds all named HTML colors to be supported by MarkWhen tags. In the event of a collision, the MarkWhen selected value will be used instead of the HTML value. The previously declared COLORS array has been renamed to MARKWHEN_COLORS and is used in the other same places, mainly to cycle through fallabck colors if a user-specified color is wrong.

This also adds a new tag color syntax: html(<name>). This can be used to force selection of the HTML-variant of the color name instead of the MarkWhen-variant.

[zjijz]

@kochrt Let me know how I can test this to verify it doesn't break existing features and also works as intended for the new stuff.

[kochrt]

First of all, thanks for doing all this!

My initial thoughts are that I'm not particularly attached to the default colors that exist now (HUMAN_COLORS), but I'm also not really attached to html default colors either. I don't see that many people reaching for moccasin or rebeccapurple, ya know?

What if we just extended (or replaced) HUMAN_COLORS to have some more variety with some easier names, like red1, red2, ... red10, gray1 ... gray10, etc., increasing in darkness? I tend to instinctively reach for tailwind but I'm sure there are other palette examples out there.

If we did something like that we could avoid the additional html(...) syntax.

What do you think?

[kochrt]

https://yeun.github.io/open-color/ just found this while rummaging around excalidraw stuff