Bug 1759982 (rhel9-modern-pkcs12)

Description of problem:
The common encryption settings for PKCS#12 files is to use pbeWithSHA1And40BitRC2-CBC algorithm (a.k.a PBE-SHA1-RC2-40) for encrypting the certificate and pbeWithSHA1And3-KeyTripleDES-CBC algorithm (a.k.a PBE-SHA1-2DES)  for encrypting the key.
Both of those algorithms are very old and far from currently recommended cryptographic practice. If we want to remove them in the future, we need to first not create more files encrypted using those algorithms.

Version-Release number of selected component (if applicable):
RHEL-8

How reproducible:
always

Steps to Reproduce:
1. export or create PKCS#12 file with keys
2. openssl pkcs12 -passin pass: -passout pass: -in /tmp/cert.p12 -out /dev/null -info -noout
3.

Actual results:
File encrypted with pbeWithSHA1And40BitRC2-CBC and pbeWithSHA1And3-KeyTripleDES-CBC

Expected results:
The file should use AES-128-CBC with PBKDF2 and SHA-256:

MAC: sha256, Iteration 600000
MAC length: 32, salt length: 8
PKCS7 Encrypted data: PBES2, PBKDF2, AES-128-CBC, Iteration 600000, PRF hmacWithSHA256
Certificate bag
PKCS7 Data
Shrouded Keybag: PBES2, PBKDF2, AES-128-CBC, Iteration 600000, PRF hmacWithSHA256

Additional info:
This is a tracking bug, it applies to all applications and libraries that produce PKCS#12 files.

It is not about removing support for old algorithms, just about changing the defaults. Since this change is expected to bring interoperability issues, we do not want to perform it during RHEL-8 life, but introduce it with next major release.

Increasing the iteration count above 600K is not recommended, it's known to cause interoperability issues with Windows (that is their maximum), see https://bugzilla.mozilla.org/show_bug.cgi?id=1278071#c31

This change will also automatically make the PKCS#12 files compatible with FIPS.