Description of problem:
OpenSSL still supports RSA encryption and decryption without padding, which is not part of any of the FIPS standards except for the use-case as RSASVE (which is a separate function in both the provider and the libcrypto API).

Version-Release number of selected component (if applicable):
openssl-3.0.1-44.el9_0.1

How reproducible:
Run openssl/Regression/bz2053289-FIPS-provider-doesn-t-block-RSA-encryption-for-key across, check "RSA-2048 pad=none en/decryption: allowed in FIPS" – it should not succeed

Steps to Reproduce:
1. openssl genpkey -algorithm rsa -pkeyopt rsa_keygen_bits:2048 -out rsa.pem
2. dd if=/dev/zero of=data bs=1 count=256 (Note /dev/zero; if you use /dev/urandom there's a chance this will fail because the data is larger than the modulus).
3. openssl pkeyutl -encrypt -pkeyopt rsa_padding_mode:none -inkey rsa.pem -in data -out /dev/null

Actual results:
Call succeeds, encryption is performed

Expected results:
Call fails if FIPS mode, or provides an indicator that supports querying whether this was an approved operation.

Additional info:
RSASVE uses a different entrypoint into the provider, but RSA-OAEP padding and RSASSA-PSS signatures seem to compute the padding in libcrypto and then call into the provider with a none padding mode, so this may lead to issues.