doc: remove invalid padding from crypto.publicDecrypt

[jtousley]

#9609 and #9611 should also apply to publicDecrypt.

Original issues:
#9588 and #1093

[BridgeAR]

Ping @nodejs/crypto

[bnoordhuis]

The docs for crypto.publicDecrypt() are correct, aren't they?

  - `padding` {crypto.constants} An optional padding value defined in
    `crypto.constants`, which may be: `crypto.constants.RSA_NO_PADDING` or
    `crypto.constants.RSA_PKCS1_PADDING`.
...
Otherwise, this function uses `RSA_PKCS1_PADDING`.

Both padding types are supported. The caveat emptor for RSA_NO_PADDING is that the ciphertext's size needs to match the key's.

edit: see #27188 for regression tests.

[jtousley]

My apologies, I had thought the other issues referenced the document version. This issue is specific to older versions of the documentation (v4-7.x). The current version is up to date as you say.
For those older versions, the padding types for privateEncrypt and publicDecrypt should match. #9609 seems to have resolved privateEncrypt, but left publicDecrypt alone.

[tniessen]

The only affected version (that we still support) is v6.x which will be at EOL at the end of the month. I assume there will not be a fix for a documentation issue few days before EOL and strongly recommend to switch to a more recent LTS branch.