fix(linter/unicorn/prefer-string-raw): skip fix for TSPropertySignature keys

[camc314]

Summary

• prevent unicorn/prefer-string-raw from rewriting TypeScript property signature keys into invalid tagged-template syntax
• add a regression case based on the PostHog ecosystem CI failure
• preserve existing behavior for runtime string expressions

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[camc314]

Merge activity

• Jul 13, 2:09 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Jul 13, 2:12 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Jul 13, 2:18 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Jul 13, 2:20 PM UTC: camc314 added this pull request to the Graphite merge queue.
• Jul 13, 2:25 PM UTC: Merged by the Graphite merge queue.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 93c3cc0a25

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[codspeed-hq]

Merging this PR will not alter performance

✅ 5 untouched benchmarks
⏩ 66 skipped benchmarks¹

---

_{Comparing codex/fix-prefer-string-raw-ts-property-key (93c3cc0) with main (e86e0d8)²}

Footnotes

1. 66 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. No successful run was found on main (df67932) during the generation of this report, so e86e0d8 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩