Fix Workflows for Crypto Refresh and PQC configurations

[kaie]

You have a workflow that uses this image:
- { name: 'Fedora 40', container: 'fedora-40-amd64', backend: 'Botan', botan_ver: '3.3.0', pqc: On, gpg_ver: 'system' }

However, the code from PR #2355 requires at least botan 3.6.0 when PQC is enabled.

I suggest that you either turn pqc: Off for above image, or that you change botan_ver to 3.6.0 (or higher).

Which one do you prefer @ni4

Example failing workflow:
https://github.com/rnpgp/rnp/actions/runs/26102542153/job/76757268622?pr=2355

[EmanuelLoos]

What is the status on PQC support in rnp and Thunderbird? Websites and messengers are already deploying PQC in production, even GnuPG has a stable release supporting PQC, but somehow OpenPGP email encryption lags behind, because Thunderbird still seems unable to support it in any way. Even when configured with external GnuPG and a GnuPG version that supports PQC, it does not work in the latest ESR release because Thunderbird seems unable to find ECC+Kyber keys of external GnuPG installations. So when can PQC support be expected to arrive in Thunderbird? Will it be included in the next ESR version?