alternate colormap mechanism

the current way of loading the colormap as an import has the drawback that it is blocking the LCP load and also renders the free selection of an arbitrary color via its hex value somewhat impaired. i think a more general approach might be to calculate the lightness the hex value by averaging the r, g, b values and decide based on that if the `color` needs to be light or dark.
alternatively, moving the colorMap into `scripts.js` would remove the performance impact.

Inspect how the colormap is currently imported and how `scripts.js` handles related color behavior. Compare the proposed lightness calculation with moving the colormap into `scripts.js`; the work is done when arbitrary hex colors no longer impair light/dark selection and the colormap no longer blocks LCP.

Written by the indexing model from the issue text.