[FEAT] Define other frontmatter color_formats

[ninetailedtori]

This PR is focused on one thing in particular: simplification of syntax. Current solution for polling colours in other formats is use of ., and if we use .hex, we can customise that. Using other formats causes issues which are solved by writing a whole macro into the structure. What I propose is:

• allow users to define "hex_format", "rgb_format", "hsl_format", etc for all color outputs.
• this then reduces the need for a whole macro, making all the tera styles we have easier.
• users then can display several formats, for rgb, hsl, hex, with the correct format for all.

The solution I had once before was refactoring hex_format to a color_format, but the issue is, I think that some tera styles DO use multiple formats? Which would break this. But if this might be wrong, we could do that:

• remove hex_format
• replace with color_format
• have values such as hex.r, rgb.b, hsl.l, hex.a, rgb.a, oklch.c, etc.

Would love to hear opinions on this!

[backwardspy]

tera makes it so that we can't simply do for other colour representations what we have done for hex; there is no way to customise the string value of a non-primitive value rendered in the template.

there is a sort of workaround idea that i've been considering for a while, i'll revisit as part of this issue and see how it looks.

[ninetailedtori]

tera makes it so that we can't simply do for other colour representations what we have done for hex; there is no way to customise the string value of a non-primitive value rendered in the template.

there is a sort of workaround idea that i've been considering for a while, i'll revisit as part of this issue and see how it looks.

ooh, I see. I'm curious as to how you'll work around that then! feel free to attach any PR to this issue :]