Handle incorrectly versioned certificates in system truststore

[CRogers]

Before this PR

Similar to #168. Someone internally has this x509 cert in their system truststore issued by StrongLoop. The cert uses v3 extensions but only lists itself as being v1. Java is very strict on this:

Caused by: java.security.cert.CertificateParsingException: no more data allowed for version 1 certificate
	at java.base/sun.security.x509.X509CertInfo.parse(X509CertInfo.java:679)

The printed form of the cert:

$ openssl x509 -in gradle-jdks/src/test/resources/strongloop-cert-with-v3-extensions-but-v1-version.pem -text
Certificate:
    Data:
        Version: 1 (0x0)
        Serial Number: 6606 (0x19ce)
    Signature Algorithm: sha1WithRSAEncryption
        Issuer: C=US, ST=CA, L=San Francisco, O=StrongLoop, Inc., OU=StrongOps, CN=ca.strongloop.com
        Validity
            Not Before: Dec  8 23:35:33 2015 GMT
            Not After : Apr 24 23:35:33 2043 GMT
        Subject: CN=strongloop.com
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                RSA Public-Key: (2048 bit)
                Modulus:
                    // snip
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Subject Alternative Name:
                IP Address:0.0.0.0, IP Address:127.0.0.1

After this PR

==COMMIT_MSG==
Fix errors of the form no more data allowed for version 1 certificate when the system truststore has incorrectly versioned X.509 certs in it.
==COMMIT_MSG==

We just ignore these ones - they are not going to be the Palantir CA.

Possible downsides?

[changelog-app]

Generate changelog in changelog/@unreleased

Type

• Feature
• Improvement
• Fix
• Break
• Deprecation
• Manual task
• Migration

Description

Fix errors of the form no more data allowed for version 1 certificate when the system truststore has incorrectly versioned X.509 certs in it.

Check the box to generate changelog(s)

• Generate changelog entry

[svc-autorelease]

Released 0.32.0

[carterkozak]

we may want to check that e.getMessage() doesn't return null prior to the .contains invocation