Update programming language colors and metadata

changed milestone to %13.5

	3 Warnings
	This merge request is quite big (more than 1460 lines changed), please consider splitting it into multiple merge requests.
	New migrations added but db/structure.sql wasn’t updated. Usually, when adding new migrations, db/structure.sql should be updated too (unless the migration isn’t changing the DB schema and isn’t the most recent one).
	You’ve made some app changes, but didn’t add any tests. That’s OK as long as you’re refactoring existing code, but please consider adding any of the ~”tooling”, ~”tooling::pipelines”, ~”tooling::workflow”, ~”documentation”, ~”QA” labels.

Reviewer roulette

Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category (e.g. frontend or backend), and by a maintainer in all other categories.

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited, or the chosen person is unavailable.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.

Category	Reviewer	Maintainer
database	Steve Abrams (`@sabrams`) (UTC-6, 8 hours behind `@zj-gitlab`)	Toon Claes (`@toon`) (UTC+2, same timezone as `@zj-gitlab`)
backend	Valery Sizov (`@vsizov`) (UTC+2, same timezone as `@zj-gitlab`)	Shinya Maeda (`@shinya.maeda`) (UTC+7, 5 hours ahead of `@zj-gitlab`)