feat: build .deb and .rpm release files

[phm07]

This PR adds the following package files to releases:

• hcloud-cli-1.59.0-1.aarch64.rpm
• hcloud-cli-1.59.0-1.x86_64.rpm
• hcloud-cli_1.59.0_amd64.deb
• hcloud-cli_1.59.0_arm64.deb

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 51.49%. Comparing base (7756f5d) to head (9365b15).

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #1311       +/-   ##
===========================================
- Coverage   72.43%   51.49%   -20.95%     
===========================================
  Files         301      295        -6     
  Lines       11005    10750      -255     
===========================================
- Hits         7972     5536     -2436     
- Misses       2144     4674     +2530     
+ Partials      889      540      -349     

Flag	Coverage Δ
e2e	51.49% <ø> (ø)
unit	?

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.

[phm07]

Some considerations:

• Right now goreleaser generates a lot of package files, because it generates one for each architecture. We might want to limit those, amd64 and arm64 would probably be enough. (We still offer direct binary downloads for all architectures anyway)
• Packages are not signed yet. This causes a problem on alpine for example: ERROR: hcloud-cli_1.59.0_x86_64.apk: UNTRUSTED signature. We'd need to create a key and provide it to users so they can install it

[phm07]

The manpage output (as well as the generated markdown docs) would have a way better table view if the tables are printed using markdown format. Our table renderer already supports this, we just need to find a way to switch between the pretty print and markdown. I used a custom config option for now but it doesn't seem to work, because viper is not loaded if you only generate docs/manpages. I'll have a look at this another time.

[apricote]

There is still something weird going on with the option table, the rows and columns are not consistent, see no-experimental-warnings and poll-interval

[apricote]

What do you think about running this and completions.sh as part of go generate and dump the generated files in dist/{manpages,completions}?

Related to the above, is there a reason to put these two files and internal/scripts/generate_docs.go in separate places? They feel pretty related.

[phm07]

Yes, it could use some clean up, I'll do that

[phm07]

Two things:

• Goreleaser requires dist/ to be empty, even after the before hooks. So we probably can't (easily) put our generated files there
• Why do we want to go generate the manpages and completions? We don't want to commit them into the repository and they are only needed for a release anyway. Only generating manpages and completions is pretty fast, but running a full go generate before each release would be slow.