fix(linter/switch-case-braces): add support for string including colon on case expression

[Lukinoh]

What version of Oxlint are you using?

1.14.0

What command did you run?

oxlint --type-aware --fix

What does your .oxlintrc.json config file look like?

{
  "plugins": ["unicorn"],
  "rules": {
    "unicorn/switch-case-braces": "error"
  }
}

What happened?

The rule unicorn/switch-case-braces does not behave as expected.
The following case was wrongly formatted.

// Input
case "scope:type":
  // ...
  break;

// Observed
case "scope: {type":
  // ...
  break;
}

// Expected
case "scope:type": {
  // ...
  break;
}

How was it fixed?

I used a regex to determine where is the colon instead of relying on the first colon found.

Disclaimer: I have really low experience with Rust, maybe there was a smarter way of doing it I missed.

[graphite-app]

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #13687 will not alter performance

_{Comparing Lukinoh:fix-lint-unicorn-switch-case-braces (1288958) with main (a21ff54)¹}

Summary

✅ 37 untouched

Footnotes

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

[Lukinoh]

I fixed the problem related to having the regex inside the for loop.
Is it possible to rerun the checks, please.

[Lukinoh]

An idea to remove the regex overhead in performance is just to not use it 🙂.
Instead, we could revert to use find.
We use find on the iteration of the following pattern ["`:", "':", "\":", ":"] and stop at the first match.

wdyt?