build: spotbugs-maven-plugin 4.10.5.0

[bernardladenthin]

Summary

• spotbugs-maven-plugin 4.10.4.1 -> 4.10.5.0 (SpotBugs 4.10.5, the first release that reads JSpecify), in step with the sibling repositories. Nothing to report here: the new nullness detectors find no Lombok-generated equals under @NullMarked in this repository, so no lombok.config is involved. CHANGELOG entry.

Test plan

• Affected unit / integration tests pass locally: mvn clean compile spotbugs:check is green with 0 bugs.
• CI is green on this branch
• Docs / CHANGELOG updated where applicable

Related issues / PRs

Same sweep in the sibling repositories: bernardladenthin/java-llama.cpp#533 (spotbugs-maven-plugin 4.10.5.0, JSpecify nullness on Lombok-generated code, JLine 4.4.8, llama.cpp b11558 -> b11574), bernardladenthin/BitcoinAddressFinder#387 (spotbugs-maven-plugin 4.10.5.0, the same Lombok answer, a static ReaderProgress), bernardladenthin/srcmorph#225 (spotbugs-maven-plugin 4.10.5.0, checker-qual 4.3.1, the same Lombok answer) and bernardladenthin/workspace#55 (the canonical lombok.config, the tool-version row).

Checklist

• I have read CONTRIBUTING.md and CODE_OF_CONDUCT.md
• My commits follow Conventional Commits
• No security-sensitive changes (if there are, I have notified the maintainer privately per SECURITY.md)

🤖 Generated with Claude Code

https://claude.ai/code/session_01AytmJF9faEiQEVt6eetQS2

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud