Use GitHub Actions matrix feature to build and release

[ghost]

All CI execution time reduced to 3 minutes

• Removed s390x, ppc64 and ppc64le by the way
• Removed the MIPS SoftFloat by the way
• Transfer from v2fly/V2FlyBleedingEdgeBinary to GitHub Actions Artifact
  • See https://github.com/v2fly/v2ray-core/actions/runs/388904443 (requires GitHub account to download)
• Rewrite the signature script a little bit: afdd5ac Not tested (it theoretically works)
• Migrate from Bazel to go build compilation (Okay, Bazel can be removed

[Loyalsoldier]

You can check my build results out here:

https://github.com/Loyalsoldier/v2ray-core/actions/runs/389419962
https://github.com/Loyalsoldier/v2ray-core/releases/tag/v4.33.5

[ghost]

LGTM, Do we need to test the release process?

[Loyalsoldier]

LGTM, Do we need to test the release process?

Not necessary. BTW, what about reproducible build?

[ghost]

Those binaries are built via go build ... which is exactly what Bazel was doing (previously)
This should not be a problem.

I'm not familiar with the verification prodeture of a reproducible build. I'm hoping someone could help me verifying it.