Clarify release executables' target, provide statically linked ones

[sanmai-NL]

It is not clear from the releases page for what architecture the binary executables listed there are suitable.
Neither is it clear that they are dynamically linked. Because of the latter they do not work under Alpine Linux without jumping through hoops. Seems like this situation makes users miss out on a major use case for docker2aci, running inside Alpine Linux based build containers.

Can you clarify this and release statically linked, stripped executables?

[lucab]

As we can't cover here all possible combinations/usecases, binaries provided via GH are just shortcuts for one of the (arbitrarily chosen) most common case. As we are distributing the source here, binaries can be properly built by maintainers for any specific case (and that is the usual recommend distribution/installation mean wherever a package manager is available, like in alpine).

That said, the dynamic executable in here doesn't seem to be on purpose and could be easily turned into a static one by prepending a CGO_ENABLED=0 to the build script. If you are interested in that, would you mind submitting a short PR just doing that? That way, next release could be shipping a static executable.