gnupg: update to 2.4.4

[filiprojek]

just a version bump
tagging the maintainer @jcgruenhage

Testing the changes

I've done the following regression testing:

• encrypt/decrypt
• key import/export
• keyserver sync
• symmetric encryption/decryption
• non-resident key (yubikey gen5)

No regresions found.

Local build testing

• I built this PR locally for my native architecture, (x86_64-glibc)

[jcgruenhage]

Even if it's just a version bump, don't merge this without checking extensively what they changed upstream.

-----BEGIN ALLEGATIONS-----

GnuPG has allegedly made changes in the past that were inconsistent with the OpenPGP standard in a way that deliberately breaks interoperability with other OpenPGP implementations with the alleged goal of weaponizing they userbase against other implementations to get their way with how the standard is supposed to develop in the future.

-----END ALLEGATIONS-----

We're patching out changes like that already, and we need to be careful with updates to make sure we don't accidentally include updates like that without patching out the unwanted stuff. This is done consistently with other distros as well, with at least Alpine, Arch, Fedora and NixOS shipping a patched version like this. I'm not sure who else also patches GnuPG, but there's going to be a few more I suspect.

[filiprojek]

I've added some regression tests to the original PR description. I'm not sure what else to test. The changelog does not have to appear to have any breaking changes listed.

[realcharmer]

We also do quite a bit of patching in SUSE: https://build.opensuse.org/package/show/openSUSE%3AFactory/gpg2

[github-actions]

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.