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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
Roslynator.Analyzers	4.12.9 -> 4.13.1

---

Release Notes

dotnet/roslynator (Roslynator.Analyzers)

v4.13.1

Added

• Support custom path of a test file (PR)
  • It's possible to specify a directory path and/or a file name of a test file.
  • Applies to testing library (Roslynator.Testing.*).

v4.13.0

Fixed

• Fix analyzer RCS1229 (PR)
• Fix analyzer RCS1174 (PR)
• Fix analyzer RCS0010 (PR)
• Fix analyzer RCS0005 (PR)

Added

• Add analyzer "Put expression body on its own line" RCS0062 (PR by @​cbersch)
  • Affects analyzer RCS1016
  • Affects refactoring RR0169

Changed

• Move analyzer RCS1036 to Formatting.Analyzers as RCS0063 (PR)
  • Old analyzer still works but is marked as obsolete.
• Bump Roslyn to 4.12.0 (PR)
  • Applies to CLI and testing library.
• Bump Microsoft.Build.Locator to 1.7.8 (PR)

v4.12.11

Added

• [CLI] Add support for .NET 9 (PR)

Fixed

• Fix refactoring 'Change accessibility' (RR0186) (PR)
• Fix analyzer RCS1264 (PR)

Changed

• Move DiagnosticRules and DiagnosticIdentifiers to Roslynator.Common (PR)

v4.12.10

Fixed

• Fix analyzer RCS1213 (PR)
• Improve code fixer for RCS1228 (PR)
• Fix diagnostic message for RCS0032 (PR)

Changed

• Update whitespace formatting rules (PR)
• Ensure that diagnostics are not reported with zero length (PR)

---

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 becomes conflicted, 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.