fix: ensure go binaries have vcs information

[jooola]

• https://goreleaser.com/cookbooks/build-go-modules/#building-go-modules
• Do not run go mod tidy just before the build
• Fetch the entire git history to make sure

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.64%. Comparing base (d96cd20) to head (84e7edf).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1367   +/-   ##
=======================================
  Coverage   72.64%   72.64%           
=======================================
  Files         300      300           
  Lines       11051    11051           
=======================================
  Hits         8028     8028           
  Misses       2129     2129           
  Partials      894      894           

Flag	Coverage Δ
e2e	51.34% <ø> (+<0.01%)	⬆️
unit	67.58% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ 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.

[apricote]

The link mentions under "Limitations":

VCS info will not be available.

This conflicts the PR title

[jooola]

Yes, the docs for this is confusing. Though Github issues seem to point to this documentation to fix this particular case.

I need to test this locally.