Set monochromatic colour maps to the same lightness range

[MBravoS]

Toying around with the new manipulation tools (#1 ) it became obvious that we should set as many of our colour maps to the same lightness range. Since we now have the tools to encourage the user to create new colour maps, they should mix together nicely, without jumps in lightness. I settled on a 0.1<L*<0.9 range as that is the most common among our colour maps, and made new versions for maps not using that range (Blue, Cyan, Green, Magenta, Orange, Stone and Yellow), with the .jscm files and visualisations in my development branch.

Discussing this with @AstroRobin there is no obvious reason to generate near-duplicate maps, so these would be replacing the current ones. I'm not including Garnet, Tropical and Ripe in this remake, as those have shortened dynamic ranges by design.

[AstroRobin]

We need to consider whether Cyan can still remain as one of the base monochromatic colourmaps once we rescale the lightness range. Cyan has the annoyance that it quickly moves into "teal" or "light blue" (subjective) as it moves into the darker regime. Either we keep scicm.Cyan as a colour map and ensure that scicm.Blue does not venture into cyan territory at the light end, or we also introduce/replace with scicm.Teal or something of the like, which acts as the middle point between blue and green.

[MBravoS]

I made the bright end of the Blue_1090 colour map closer to light blue, would that be enough? As for cyan, I'm happy to rename the current Cyan_1090 to teal, but I'm not sold on having an additional cyan map. If you could make a 10-90 version for me to see that would be great.

[AstroRobin]

Here are the colour names for Blue_1090 in 20 increments:
('navy blue', '#001146', '#020f3e')
('navy blue', '#001146', '#071950')
('marine', '#042e60', '#0e2363')
('marine', '#042e60', '#152c79')
('sapphire', '#2138ab', '#1b348e')
('sapphire', '#2138ab', '#213ca6')
('blue blue', '#2242c7', '#2445bd')
('azul', '#1d5dec', '#1b54c6')
('mid blue', '#276ab3', '#1b62c7')
('medium blue', '#2c6fbb', '#2270c8')
('windows blue', '#3778bf', '#2a7cca')
('cerulean', '#0485d1', '#3489cd')
('azure', '#069af3', '#3f95d1')
('azure', '#069af3', '#4aa2d5')
('lightblue', '#7bc8f6', '#55aeda')
('lightblue', '#7bc8f6', '#62bcdf')
('bright sky blue', '#02ccfe', '#71c8e4')
('neon blue', '#04d9ff', '#85d4ea')
("robin's egg blue", '#98eff9', '#9adfef')
('pale sky blue', '#bdf6fe', '#aeebf6')

Whereas before, our colours were ending in cyans. So I think Blue_1090 is now perfect.

I will toy around with making a Cyan 10-90 map.

[AstroRobin]

I've added a Cyan_1090 colourmap to devel_robin, which looks reasonably good. I've managed to capture mostly cyan and turquoise colours with little contamination of teal.

The named colours for this map are:
('almost black', '#070d0d', '#062023')
('dark blue grey', '#1f3b4d', '#0c292d')
('dark blue grey', '#1f3b4d', '#123237')
('dark teal', '#014d4e', '#1c434b')
('deep teal', '#00555a', '#214b54')
('petrol', '#005f6a', '#24545e')
('petrol', '#005f6a', '#2b6771')
('deep aqua', '#08787f', '#2e707a')
('dark cyan', '#0a888a', '#33838b')
('dark cyan', '#0a888a', '#358d94')
('sea', '#3c9992', '#37979d')
('sea', '#3c9992', '#38a1a6')
('turquoise blue', '#06b1c4', '#39acb1')
('turquoise blue', '#06b1c4', '#39b7ba')
('topaz', '#13bbaf', '#39c2c4')
('aqua blue', '#02d8e9', '#37cdce')
('aqua blue', '#02d8e9', '#35d9d9')
('bright light blue', '#26f7fd', '#31e5e4')
('bright cyan', '#41fdfe', '#2bf1ef')
('bright turquoise', '#0ffef9', '#21fefa')

[MBravoS]

I replaced the old colour maps and added both Teal and Cyan in version 0.6.0 (now live).