Add riscv64 & loong64 for goreleaser

[znley]

No description provided.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 19.38%. Comparing base (bcc7c78) to head (1ea73fe).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3072      +/-   ##
==========================================
- Coverage   19.49%   19.38%   -0.12%     
==========================================
  Files         646      646              
  Lines       54504    54504              
==========================================
- Hits        10625    10565      -60     
- Misses      43340    43411      +71     
+ Partials      539      528      -11     

Flag	Coverage Δ
codegen-oldstable-canary-fixtures	?
codegen-stable-canary-fixtures	?
unit-oldstable	82.80% <ø> (+<0.01%)	⬆️
unit-stable	19.38% <ø> (ø)

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.

[fredbi]

@znley I don't think we actually use goreleaser for our release process (a pity I'd say, but that's the way it is now).
believe tha the goreleaser config is a remnant of a past attempt to use goreleaser.

[znley]

@fredbi
Now I get it! So what method is used now for release?

[fredbi]

I believe that is the tool used by @casualjim to cut releases: https://github.com/go-openapi/github-release

[znley]

@fredbi @casualjim
The github-release seems to be used for upload binaries and gorelease is used for building, is right?