chore(deps): update dependency roslynator.analyzers to 4.15.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
Roslynator.Analyzers	4.14.0 -> 4.15.0

---

Release Notes

dotnet/roslynator (Roslynator.Analyzers)

v4.15.0

Added

• Add option roslynator_null_conditional_operator.avoid_negative_boolean_comparison (PR)
  • Do not suggest to use null-conditional operator when result would be ... != true/false
  • Applicable for RCS1146

Fixed

• Fix analyzer RCS1172 (PR)
• [CLI] Fix loc command (PR)
• Exclude ref-field backed properties from RCS1085 (PR by @​ovska)
• [CLI] Fix rename-symbol scope option not being applied correctly (PR by @​andrtmschkw)
• [CLI] Fix rename-symbol support for top-level statement (PR by @​andrtmschkw)

Changed

• Migrate to .NET 10 (including command-line tool) (PR)

v4.14.1

Added

• [CLI] Add support for slnx files (PR by @​darthtrevino)
  • Bump Roslyn to 4.14.0
  • Drop support for .NET 7 SDK

Fixed

• Fix analyzer RCS1246 (PR)
• Fix analyzer RCS1248 (PR)
• Fix analyzer RCS1203 (PR)
• Fix analyzer RCS1043 (PR)
• Fix analyzer RCS1213 (PR)
  • Add unity method OnRectTransformDimensionsChange
• Fix analyzer RCS1253 (PR)
• Fix refactoring Check expression for null (PR)

Changed

• Change behavior of analyzer RCS1206 (PR)
  • The condition for option omit_when_single_line will be that the braces/brackets are on the same line, not just the expression in the braces/brackets

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.