Fix jackson NPR assertion in JDK 17

[pranavbhole]

Fixes #XXXX.

Description

fixing test in master, Looks like JsonProcessingException from jackson throws more specific assertion with reason in the case of the just null point exception. With older JDK, jackson throws generic NPR in deserialization. Adding the JDK conditional assertions.

Fixed the bug ...

Renamed the class ...

Added a forbidden-apis entry ...

Release note

---

Key changed/added classes in this PR

• MyFoo
• OurBar
• TheirBaz

---

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.
• a release note entry in the PR description.
• 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.

[somu-imply]

Also can change this message contains to

Cannot construct instance of `org.apache.druid.segment.column.ColumnSignature

which I think would be same for all the JVM versions

[pranavbhole]

We can shorten the message as well. That will also work. I just want to highlight the fact that jackson is not bubbling up the generic NPR for jdk version >17 and giving specific root cause of the NPR exception.

[imply-cheddar]

Can we change the source of the exception to do something that doesn't cause NPEs? There's no way that an end user woudl actually understand what s is and why it needs length called on it. Come to think of it, there's probably no reason to believe that they would even understand what an org.apache.druid.segment.column.ColumnSignature is...