Find a solution to preserve shortcut casing during download

[coderabbitai]

Summary

The current fix for shortcut capitalization is ineffective. The shortcut values are already capitalized when the definitions repository downloads them.

Find and implement a solution that preserves the intended shortcut casing before or during the download/import process.

Rationale

Changing capitalization after the download does not correct the source data that is already capitalized. The solution must identify the upstream source or transformation that introduces the capitalization.

Affected areas

• The shortcut download or import pipeline.
• The source that provides shortcut values.
• Generated definitions that consume shortcut values.

Required changes

1. Trace where shortcut values first become capitalized.
2. Determine whether the source data or the download/import transformation causes the capitalization.
3. Implement a correction at the appropriate stage.
4. Add or update regression coverage for shortcuts whose intended casing must be preserved.

Acceptance criteria

• Downloaded shortcut values retain their intended casing.
• The generated definitions contain shortcut values with the intended casing.
• Regression coverage fails if shortcut casing is changed during download or import.

Backlinks

• Pull request: fix: do not capitalize shortcuts #89
• Requester comment: fix: do not capitalize shortcuts #89 (comment)
• Requested by: @obrusvit