release: Goreleaser configuration and automation.

[winder]

Summary

Enable goreleaser for building and publishing conduit binaries.

The automation triggers whenever a tag starting with v1. is pushed.

The previous versioning and deployment stuff seemed really complicated, and I'm really not sure what it was adding. Please let me know if this smaller process is missing any important functionality that needs to be added back.

Test Plan

I pushed a tag to my fork:

• The action ran.
• A release was published.

The downloaded binary looks good:

$ ./conduit -v
Conduit 1.0.0 (c8262a5)

[codecov]

Codecov Report

Merging #18 (f7f633d) into master (9c7f525) will increase coverage by 0.30%.
The diff coverage is 77.77%.

@@            Coverage Diff             @@
##           master      #18      +/-   ##
==========================================
+ Coverage   67.23%   67.53%   +0.30%     
==========================================
  Files          32       33       +1     
  Lines        1819     1833      +14     
==========================================
+ Hits         1223     1238      +15     
- Misses        529      530       +1     
+ Partials       67       65       -2     

Impacted Files	Coverage Δ
version/strings.go	40.00% <40.00%> (ø)
conduit/plugins/importers/algod/algod_importer.go	83.70% <100.00%> (+5.84%)	⬆️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[Eric-Warehime]

LGTM, but I'm not familiar with how the versioning bits work in Indexer so someone else should chime in on missing functionality.

[algobarb]

I guess functionally, when comparing this release (created directly from github actions) and the indexer releases, we'll lose the signed binaries and the deb packages. However, you do include the checksums, so it depends on if this is enough.

This is not my strongest area, so I am just quoting from this post:

Checksums ensure data integrity.
Digital signatures additionally ensure data authenticity.

One other thing we do that hasn't been automated is updating the release page as well: http://releases.algorand.com/

[excalq]

This seems like a useful utility, so I'm looking forward to trying in in our release process. I'm sure we'll want to make later additions. It should be useful bit of tooling towards reproducible builds.

[algobarb]

LGTM and same sentiment as @excalq