Bump slf4j from 1.7.36 to 2.0.17

[willyborankin]

Description

Bump slf4j from 1.7.36 to 2.0.17

Check List

• Functionality includes testing.
• API changes companion pull request created, if applicable.
• Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

✅ Gradle check result for f8af7b7: SUCCESS

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.85%. Comparing base (669ec8d) to head (4c4f302).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #19136      +/-   ##
============================================
- Coverage     72.96%   72.85%   -0.12%     
+ Complexity    69486    69455      -31     
============================================
  Files          5648     5648              
  Lines        319329   319329              
  Branches      46194    46194              
============================================
- Hits         232993   232637     -356     
- Misses        67516    67929     +413     
+ Partials      18820    18763      -57     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[cwperks]

Thank you for this PR @willyborankin ! The changes LGTM, just have some minor comments on the CHANGELOG entry.

[github-actions]

❌ Gradle check result for 9b9e83a: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 9b9e83a: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❕ Gradle check result for 101ae5d: UNSTABLE

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[github-actions]

❌ Gradle check result for 4c4f302: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

✅ Gradle check result for 4c4f302: SUCCESS