Do not log sensitive property value if JsonConfigurator fails to parse

[kfaraz]

Description

If a password or other sensitive information starting with a { or [ character
is specified as a property value, JsonConfigurator tries to parse it as a json
object and fails. The subsequent logs expose this sensitive information.

For example, a password starting with [ such as below

druid.escalator.internalClientPassword=[%thisisreallymypassword

would produce the following logs

2021-10-08T04:06:38,334 INFO [main] org.apache.druid.guice.JsonConfigurator - Unable to parse [druid.escalator.internalClientPassword]=[[%thisisreallymypassword] as a json object, using as is.
com.fasterxml.jackson.core.JsonParseException: Unexpected character (‘%’ (code 37)): expected a valid value (JSON String, Number, Array, Object or token ‘null’, ‘true’ or ‘false’)
 at [Source: (String)“[%thisisreallymypassword”; line: 1, column: 3]

This PR avoids logging the property value as well as the exception message as these
might contain the sensitive information (e.g. password) which could not be parsed.

---

This PR has:

• been self-reviewed.
  • using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)
• added documentation for new or modified features or behaviors.
• added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
• added or updated version, license, or notice information in licenses.yaml
• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
• added integration tests.
• been tested in a test Druid cluster.

[clintropolis]

👍

[clintropolis]

Ah this is failing CI because of coverage. I think we can skip CI because this is just a log line being adjusted here

[abhishekagarwal87]

CI failures is unrelated. Merging this PR. Thank you @kfaraz