Update hoverfly-java to 0.14.4

[scala-steward-asf[bot]]

About this PR

📦 Updates io.specto:hoverfly-java from 0.14.1 to 0.14.4

📜 GitHub Release Notes - Version Diff

Usage

✅ Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "io.specto", artifactId = "hoverfly-java" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.specto", artifactId = "hoverfly-java" }
}]

^{labels: test-library-update, early-semver-minor, semver-spec-patch, commit-count:1}

[laglangyue]

CI failed, google-cloud

[raboof]

indeed curious that Google components seem to be consistently failing with TLS errors after this update. Something to investigate.

[Roiocam]

directly using hoverfly-java cert will cause: java.security.cert.CertPathValidatorException: signature check failed

and then I customize the certificate it will complain but has a different message: Cause: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

[Roiocam]

Finally, I found the problem because hoverfly-java was updated their certificate in the jar.

I found this problem through a custom certificate, and then verified it was valid by updating the certificate.

[Roiocam]

There are still two certificates that have not been updated, my last commit updated it. The CI will be passed.

@raboof can you review this? thanks.