Code review comment for ~ubuntu-release/autopkgtest/+git/development:cross-arch-architecture-filtering

FTR: The failure was introduced by this change in Debian:
https://salsa.debian.org/debian/libgpg-error/-/commit/0c11fe4ae16c2800e13758ff1ee64c561354e628

It started to fail for i386 on autopkgtest.u.c:
https://autopkgtest.ubuntu.com/packages/libgpg-error/kinetic/i386
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/i386/libg/libgpg-error/20220523_114919_e3142@/log.gz

The relevant log is this:
```
The following packages have unmet dependencies:
 builddeps:/tmp/autopkgtest.VMjBik/1-autopkgtest-satdep.dsc:i386 : Depends: gcc-mingw-w64-x86-64:i386 but it is not installable
E: Unable to correct problems, you have held broken packages.
win64 FAIL badpkg
[...]
autopkgtest [11:49:03]: @@@@@@@@@@@@@@@@@@@@ summary
win32 SKIP Test lists explicitly supported architectures, but the current architecture amd64 isn't listed.
win64 FAIL badpkg
blame: libgpg-error
badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.
build PASS
```

As can be seen, the i386/win32 test is skipped while amd64/win64 is executed and fails with "badpkg" error due to not being able to install "gcc-mingw-w64-x86-64:i386".