I'm seeing test suite failures of ca-certificates-java which seem
unrelated to GnuPG, which fail when updating GnuPG in unstable.

In particular, i see failures like:

```
138s can-install-jre      FAIL stderr: /usr/bin/auto-apt-proxy: 176: avahi-browse: not found
```

for example in
https://ci.debian.net/packages/c/ca-certificates-java/testing/amd64/58295804/
and
https://ci.debian.net/packages/c/ca-certificates-java/testing/ppc64el/58296085/

I don't see how any of the recent changes to gpg would affect
ca-certificates-java's test suites.  gpg is not even an explicit
dependency of the relevant test suites -- it's only listed as an
explicit dependency of debian/tests/can-configure-cross-compilation, and
even there it looks to me like it could be trivially removed, by
depending on debian-archive-keyring instead, pointing to the desired
keyrings that are already in the filesystem, and not requiring keyserver
access.

I'm attaching a patch that i think should avoid the need to explicitly
depend on gpg, which should resolve matters in terms of gpg package
migration, but probably won't resolve whatever is causing the
avahi-browse problem.

I've also offered the patch at
https://salsa.debian.org/java-team/ca-certificates-java/-/merge_requests/12

Thanks for maintaining ca-certificates-java in Debian!