chore: prepare release 2.17.0

[tknopp-ld]

Summary

Prepares the 2.17.0 release by hand, same approach as 2.16.0 in #608 and 2.14.0 in #563: rulesets block the release workflow from pushing version bumps straight to main, so the bump lands as a normal PR. Tag, GitHub release, Docker Hub publish (if not already done by a release workflow run), and the downstream find-code-references Action update are done manually afterward.

Ships the /docker Action entry point from #611 so customers can override the scanner image registry (e.g. Artifactory / Docker Hub proxy).

What changed

File	Change
internal/version/version.go	2.16.0 → 2.17.0
CHANGELOG.md	[Unreleased] → 2.17.0 (2026-08-13)
build/metadata/github-actions/Dockerfile	image tag → 2.17.0
build/metadata/github-actions/README.md	find-code-references@v2.17.0 (+ /docker example image tag)
build/metadata/github-actions/docker/action.yml	default dockerImage → …:2.17.0

Behavior notes

• Bitbucket and CircleCI metadata deliberately untouched. Those publish targets remain disabled (chore: disabling gha, bitbucket publishing, unblocking docker hub release #593); bumping them would name versions that were never cut.
• GHA publish is still manual. After merge: publish Docker images / GitHub release for v2.17.0 as usual, then cp -a build/metadata/github-actions/. into launchdarkly/find-code-references (includes new docker/), commit, tag v2.17.0 (and update v2 if that is still your practice). Use git add -A so docker/action.yml is included on first publish.

Test plan

• go build ./... (version constant only)
• Diff vs main is only the five files above
• After merge + Hub image exists: sync find-code-references and confirm docker/action.yml is present at v2.17.0
• Optional: couscous smoke with published uses: launchdarkly/find-code-references/docker@v2.17.0

Made with Cursor