refactor: remove unnecessary 'switch (true)' usage

[Rel1cx]

What kind of change does this PR introduce?

• Bugfix
• Feature
• Docs
• Test
• New Binding issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes, and the changes were approved in issue #___
• No

Checklist

• When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
• I have added a convincing reason for adding this feature, if necessary

Other information

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
eslint-react	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 1, 2025 1:27am

[Copilot]

Pull Request Overview

This PR refactors the boolean-type variant detection by replacing a switch (true) block with a clearer if/else structure.

• Introduces boolean0 to hold the first boolean type and uses if/else in place of switch (true)
• Adjusts the order of literal checks (falsy first, then truthy)

Comments suppressed due to low confidence (1)

packages/plugins/eslint-plugin-react-x/src/rules/no-leaked-conditional-rendering.ts:114

• The name boolean0 is not very descriptive. Consider renaming to firstBoolean or firstBooleanType for clarity.

  const boolean0 = booleans[0];