Document label organization for better visual organization - label guide

## Problem

The repository currently lacks comprehensive documentation for its label organization. With a growing number of labels across multiple categories (issue types, platforms, areas, statuses, and more), contributors and triage team members may struggle to understand when and how to apply the correct labels. Without a clear label guide, visual organization is inconsistent, making it harder to quickly identify and prioritize issues.

## Proposed Solution

Create a comprehensive label guide document (`docs/LABEL_COLORS.md`) that catalogs ALL existing labels in the repository, organized by category. This label documentation will include:

- A complete table of all labels with their category, color, and description
- Clear grouping by label type (issue-type, platform, area, status, performance)
- Usage guidelines explaining when to use each label category
- A visual demonstration issue with ALL labels applied

This label guide will serve as the single source of truth for label organization in the repository.

## Benefits

- **Improved visual organization**: A clear label taxonomy makes the issue tracker more navigable and visually organized
- **Easier issue triage**: Team members can quickly understand the label system and apply correct labels
- **Better contributor experience**: New contributors can learn the label conventions faster
- **Consistent labeling**: Reduces confusion about which labels to use for different types of issues
- **Documentation**: A maintainable reference that can be updated as labels evolve

Create the proposed docs/LABEL_COLORS.md and start by reviewing the repository's existing GitHub labels, including their names, colors, and any descriptions. Group them into the categories named in the issue, add usage guidance for each category, and consider the work done when the document is a complete reference for applying labels consistently.

Vom Indexierungsmodell aus dem Issue-Text verfasst.