Add colorize.browser_color_names setting, reload config when changed

[rbolsius]

There are two features included with this PR.

1. colorize.browser_color_names setting to turn off colorization of browser color names (default is true, meaning color names are colorized by default)
2. reload configuration changes automatically without having to restart (applies to all config settings except colorize.activate_variables_support_beta)

Also included is a minor bug fix in CacheManager to avoid initializing _decorationsCache twice.

[KamiKillertO]

Thanks for the PR I really appreciate 😃. Configuration reload was something I really wanted to add, thanks for adding it 👍 .

I'm not sure about the setting to turn off colorization for browser color names. The main idea of my extension it's to help visualize colors in code files. I think adding a setting which prevent colorization contradicts this idea.

I also have a question for you, did you have any difficulty to read/understand the code?

[rbolsius]

I had no problem following the code. It is very clear and well organized. Wish I could say the same for all the code I read. The main reason I want this option to turn off coloring the color names is that, in my usage, the extension often colors regular words, comments, text, etc. when it is not desirable to color them. For instance, I enable the extension for markdown files since I sometimes write hex colors within markdown, but I don't want the word red or white to be colored in regular paragraphs of text. My use case may not be common, but I find it distracting to have the color names decorated, and I rarely if ever use HTML color names. Even in source files it is very hard to tell if a given token should be interpreted as a browser color name. Maybe it is possible to detect these contexts reliably for most stylesheet formats using simple regexps, but if someone wants to also use the extension for other source file formats, it is very likely that tokens that have nothing to do with browser colors will end up being decorated. Maybe it would make sense to have a separate config setting instead that lists the file formats for which color names decoration should be disabled. Thanks BTW for creating such an awesome extension!

[KamiKillertO]

Ok I see your point ^^.
🤔maybe a good solution could be to add a settings which permit to activate/deactivate colors decorations per language or file extensions.

Maybe something like :

"colorsColorization": {
  "*": [ "rgb", "hexa", "hsl", "browser", "variables"],
  "mardown": ["rgb", "hsl", "hexa"],
  // ".md": ["rgb", "hsl", "hexa"] // alternative
}

I need to think about it, I suggest you to create an issue for this and update your PR to remove everything about colorize.browser_color_names.