Changes

drop FTCBFS patch #1038165 fixed in c-ares/1.19.1-3

This reverts commit 242bc43b7bf646090df0fb2e7a330796096c4e74.

drop fixup #1035521 applied in gcc-defaults/1.206

improve usage of dpkg-architecture

 * Properly quote arguments, which also makes shellcheck a little
   happier.
 * Use the -i flag rather than matching its output.
 * When in a hook, prefer the hook argument as architecture.

drop -Wno-error MR applied to glibc/2.37-3

unconditionally apply patch_gcc_has_include_next

gcc-12 builds started failing in stage1 while compiling libgcov-merge.c
due to missing <sys/mman.h>. That header is only available in glibc
stage2, so the issue is that HAVE_SYS_MMAN_H is defined. That happens,
because the relevant configure check erroneously succeeds by using
/lib/cpp rather than the correct cpp invocation. cpp is misdetected,
because the correct cpp failed #including <limits.h>, because our
patched __has_include_next(<limits.h>) produces an error, which is gcc
bug 80755 and is fixed by this very patch. A subtle change in include
directory order made this patch important and the failure came three
layers later.

fix p11-kit FTCBFS #1040472

increase shellcheck happiness

These are relatively obvious fixes that e.g. improve compatibility with
bash, add missing quoting or use idiomatic computations.

What remains for shellcheck largely is style remarks and false
positives. For instance, we excessively modify variables in subshells to
intentionally get those changes reverted. Likewise, using variables in
single-quoted strings is not a mistake. In order to address the globbing
issues, more architectural changes would be necessary.

drop FTCBFS patch #1040472 fixed in p11-kit/0.25.0-3