[bug]: Re-build v0.3.1 release binaries from the correct staging commit

[ffranr]

The currently uploaded tag tag v0.3.1 release binaries were built using the wrong staging commit: cdd6707702788cccfe615be3b06fe34a96ce31c6. Tag v0.3.1 is at commit fec4a4025db21d2e47994ad4bff29aa5d31d02e9.

We should replace the release binaries found here with those built using the correct tag v0.3.1 staging commit.

Here's a link to new tag v0.3.1 release binaries that I've built from tag v0.3.1 at the correct commit fec4a:
https://drive.google.com/file/d/1Fhvie1FFXqYw6BCTXRRj8-3JbKiaC1nW/view?usp=sharing

The steps I used to create these new binaries:

1. Clone repo into a new directory.
2. Checkout tag v0.3.1
3. Run make docker-release tag=v0.3.1

The differences in the binaries will be very slight. The correct commit is one ahead of the commit that was used to build the current binaries.

Completing this issue will help users verify the release binaries because they will be able to rebuild those binaries from the commit associated with tag v0.3.1.

FYI, this issue was initially reported here.

[ffranr]

I think @jharveyb confirmed that he derived the same manifest hashes here: #661 (comment)

Is that still true? And if so then I'll upload these new binaries and someone else can check my work. Agreed?

[ffranr]

I've just uploaded the correct assets for release v0.3.1.