Signed-off-by: Andrew Clayton <a.clayton@nginx.com>

Wasm module is now not built for Amazon Linux 2, Debian 11 and Ubuntu
2.0.04, since it requires cmake version newer than what's available on
those OSes.  wasm-wasi-component is not affected.

This directory is needed for contribs to function.

Probably not needed now...

Signed-off-by: Andrew Clayton <a.clayton@nginx.com>

Closes: https://github.com/nginx/unit/issues/1352

It's possible to have two versions of the same package installed on
debian-based multiarch systems - e.g. i386 alongside amd64.  This means
that when getting the package status through dpkg-query we'd get a
duplicated string:

% dpkg-query -f '$${db:Status-Status}' -W libssl-dev
$installed$installed

% dpkg -l | grep libssl-dev
ii  libssl-dev:amd64                 3.0.11-1~deb12u2               amd64        Secure Sockets Layer toolkit - development files
ii  libssl-dev:i386                  3.0.11-1~deb12u2               i386         Secure Sockets Layer toolkit - development files

The fix is to explicitely check for the main architecture and, in case
for noarch (or rather all-arch in debian terms) packages, check for
special :all architecture as well.

FreeBSD introduced sha512sum binary in version 14, but with slightly
incompatible flags as compared to Linux version.  This change makes it
work in both worlds.