Fix: version passing to GoReleaser configuration

[andrzej-janczak]

fix: version passing to GoReleaser configuration

Fix version command by properly configuring GoReleaser and version injection:

• Update GoReleaser to use version constraint (~> v1) instead of 'latest'
• Fix version information injection through ldflags
• Add proper environment variable handling for Go version

This ensures the version command shows correct build information
and follows GoReleaser's best practices for version constraints.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.00%	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (c584641)	4240	1568	36.98%
Head commit (f2b48a5)	4240 (+0)	1568 (+0)	36.98% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#115)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

[andrzej-janczak]

his change to version: "~> v1" means:
You'll always get the latest v1.x.x release
You're protected from breaking changes that might come in v2.0.0
You'll automatically get bug fixes and minor improvements within the v1 series
It's more flexible than pinning to a specific version while still maintaining stability
This is what the warning was suggesting as a best practice, and it's a better approach than either using latest (too loose) or a specific version like v1.21.1 (too strict).