Bump Staticcheck to 2026.1

[stefanvacareanu7]

Summary

• Bumps the wrapped Staticcheck version from 2025.1.1 to 2026.1 (val staticcheckVersion in build.sbt).
• Regenerates docs/patterns.json (version field) and 4 docs/description/*.md files via sbt doc-generator/run, run against a locally-installed staticcheck 2026.1 (v0.7.0).
• No changes needed to the hardcoded rules list in DocGenerator.scala: per upstream's 2026.1 release notes, no checks were added, removed, or renamed between 2025.1.1 and 2026.1 — only wording tweaks (e.g. interface{} → any) and behavioral fixes to existing checks (SA1026, SA4000, SA4003, SA4030, SA5008, SA5010, ST1003, ST1019, QF1002, QF1008, QF1012).
• Did not bump codacy-engine-scala-seed / scala-xml / ujson / scalatest / CircleCI orbs / Alpine base image — out of scope for this pure Staticcheck bump, and I couldn't reliably verify newer published versions for those from this environment. Flagging in case a maintainer wants a follow-up.

Validation (local)

• sbt scalafmt::test test:scalafmt::test sbt:scalafmt::test test:compile — pass
• sbt test — 2/2 tests pass
• sbt assembly — fat-jar builds successfully
• sbt nativeImage — fails locally with DARWIN does not support building static executable images. This is a pre-existing macOS/Darwin limitation of the --static native-image flag (unrelated to this change); CI builds this via a Linux executor where it's expected to succeed.
• docker build -t codacy-staticcheck . — builds successfully

Test plan

• All CI checks pass (check_fmt_and_compile, test, package_artifacts, docker_publish_local, plugins_test)

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

The PR updates Staticcheck documentation to version 2026.1 and has been rated as up to standards by Codacy. However, there is a critical gap: the build.sbt file, which should contain the actual tool version bump, is missing from the file list despite being a primary acceptance criterion. Additionally, there are no automated tests present to verify that the engine reports the correct version or that the documentation metadata remains synchronized with the build configuration.

Test suggestions

• Verify that the engine correctly identifies its version as 2026.1 during execution.
• Ensure docs/patterns.json version field is kept in sync with the build file automatically.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify that the engine correctly identifies its version as 2026.1 during execution.
2. Ensure `docs/patterns.json` version field is kept in sync with the build file automatically.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}

[codacy-production]

_{⚪ LOW RISK}

Nitpick: This sentence is redundant as it uses both 'by mistake' and 'mistakenly' to describe the same action. Removing the second instance improves clarity.

Suggested change

	do by mistake, for example by mistakenly using os.TempDir instead
	do by mistake, for example by using os.TempDir instead