Update request for node-forge due to several security vulnerabilities

[otramony]

Is jks-js affected by the following security vulnerabilities?
These were resolved in node-forge 1.3.0.

• CVE-2022-24773 (MEDIUM): Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code does not properly check DigestInfo for a proper ASN.1 structure. This can lead to successful verification with signatures that contain invalid structures but a valid digest. The issue has been addressed in node-forge version 1.3.0. There are currently no known workarounds. https://nvd.nist.gov/vuln/detail/CVE-2022-24773

• CVE-2022-24771 (HIGH): Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code is lenient in checking the digest algorithm structure. This can allow a crafted structure that steals padding bytes and uses unchecked portion of the PKCS#1 encoded message to forge a signature when a low public exponent is being used. The issue has been addressed in node-forge version 1.3.0. There are currently no known workarounds. https://nvd.nist.gov/vuln/detail/CVE-2022-24771

• CVE-2022-24772 (HIGH): Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code does not check for tailing garbage bytes after decoding a DigestInfo ASN.1 structure. This can allow padding bytes to be removed and garbage data added to forge a signature when a low public exponent is being used. The issue has been addressed in node-forge version 1.3.0. There are currently no known workarounds. https://nvd.nist.gov/vuln/detail/CVE-2022-24772