chore(deps): update github/codeql-action action to v3.23.1

[renovate[bot]]

This PR contains the following updates:

Package	Type	Update	Change
github/codeql-action	action	minor	v3.22.12 -> v3.23.1

---

Release Notes

github/codeql-action (github/codeql-action)

### [`v3.23.1`](https://togithub.com/github/codeql-action/compare/v3.23.0...v3.23.1) [Compare Source](https://togithub.com/github/codeql-action/compare/v3.23.0...v3.23.1) ### [`v3.23.0`](https://togithub.com/github/codeql-action/compare/v3.22.12...v3.23.0) [Compare Source](https://togithub.com/github/codeql-action/compare/v3.22.12...v3.23.0)

---

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 has been generated by Mend Renovate. View repository job log here.

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (3aa0f06) 74.1% compared to head (a930401) 75.6%.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #955 +/- ## ======================================= + Coverage 74.1% 75.6% +1.4% ======================================= Files 235 235 Lines 10056 10056 Branches 986 986 ======================================= + Hits 7455 7604 +149 + Misses 2334 2182 -152 - Partials 267 270 +3 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[github-actions[bot]]

👋 Hi! It looks like you modified some files in the Detectors folder. You may need to bump the detector versions if any of the following scenarios apply:

• The detector detects more or fewer components than before
• The detector generates different parent/child graph relationships than before
• The detector generates different devDependencies values than before

If none of the above scenarios apply, feel free to ignore this comment 🙂