Cockpit can use self-generated certificates or external certificates. We need to add a test to Cockpit which verifies that

• hybrid key exchange does not break existing use cases,
• applications work with ML-DSA certificates,
• components support both classic and post-quantum certificate chains

The automated test must work on RHEL 10 branch.

We must ensure that it passes on RHEL 10.1 RC. But for 10.1 it can be verified manually.

Upd:

• We need to test that cockpit-tls can work with post-quantum custom key pair (it needs to support multiple keys )