Make colour aliases IDE-friendly

[Timmmm]

Fixes #2049

Overview: What does this pull request change?

Makes colour aliases like BLUE more tool friendly (e.g. in VSCode).

Motivation and Explanation: Why and how do your changes improve the library?

See #2049

Links to added or changed documentation pages

Further Information and Comments

No idea why the grey order was A, B, C, E, D in the old code lol.

Reviewer Checklist

• The PR title is descriptive enough for the changelog, and the PR is labeled correctly
• If applicable: newly added non-private functions and classes have a docstring including a short summary and a PARAMETERS section
• If applicable: newly added functions and classes are tested

[GameDungeon]

While I wholeheartedly agree with this change, some other tried to fight it in the past for reasons I've now forgotten.

[vvolhejn]

I like this! I wish manim was less magical in other places as well (mobject.animate mostly)

[Timmmm]

Yeah 100% agree about animate. Hopefully we can just add manual type annotations for those magically generated methods.

[Timmmm]

Maybe I'm missing something but why does this still say Review required but GameDungion has approved it?

[GameDungeon]

I'm not an admin, it needs at least one person with commit privileges. That person takes the other reviewers into account.

[behackl]

Eventually, I would like to improve our cluttered namespace and, for example, make people use colors from an enum. But well, this is not today, and the change here is a fine quality of life improvement (and it is not like we change the available colors very often).

I'll approve this, and if there are no concerns until later today, I'll merge it so that it is included in the upcoming release.

Thank you for your contribution!

[Timmmm]

Wait, ignore my last comment; thought we were on a different PR. This one is good to go!