There's several changes to make sure plugin provides better user-experience when it comes to logging.
The main motivator for the change set are key issues such as `java.lang.IllegalArgumentException: File does not contain valid private key` which are only logged upstream at a debug level (see #400).
Thus to improve the logger experience there's 3 set of changes:
- log when plugin's SSL context builder fails (user can easily spot key format errors)
- make sure we log configuration errors before raising them (due https://github.com/elastic/logstash/issues/12484)
- on SSL hand-shake failures extract the real-cause as an attempt to log a better info message e.g.
Co-authored-by: Rob Bavey <[email protected]>
