[improve] Implement negative cache to avoid repetitive failure

[aymkhalil]

In pulsar transformation, some errors are only detected at runtime. Those could lead the function to be stuck with high CPU utilization until the error is resolved. Some of those errors are sticky in nature an require user intervention. For example:

2023-01-17T20:32:50,787+0000 [**/**/**] WARN  org.apache.pulsar.functions.instance.JavaInstanceRunnable - Encountered exception wh │
│ java.lang.IllegalStateException: Flatten requires non-null schemas!                                                                                │
│     at com.datastax.oss.pulsar.functions.transforms.FlattenStep.validateAvro(FlattenStep.java:68) ~[?:?]                                           │
│     at com.datastax.oss.pulsar.functions.transforms.FlattenStep.process(FlattenStep.java:43) ~[?:?]                                                │
│     at com.datastax.oss.pulsar.functions.transforms.TransformFunction.process(TransformFunction.java:259) ~[?:?]                                   │
│     at com.datastax.oss.pulsar.functions.transforms.TransformFunction.process(TransformFunction.java:249) ~[?:?]                                   │
│     at com.datastax.oss.pulsar.functions.transforms.TransformFunction.process(TransformFunction.java:121) ~[?:?]                                   │
│     at org.apache.pulsar.functions.instance.JavaInstance.handleMessage(JavaInstance.java:94) ~[com.datastax.oss-pulsar-functions-instance-2.10.2.3 │
│     at org.apache.pulsar.functions.instance.JavaInstanceRunnable.run(JavaInstanceRunnable.java:321) ~[com.datastax.oss-pulsar-functions-instance-2 │
│     at java.lang.Thread.run(Thread.java:829) ~[?:?]

Flatten strictly work with schema, and until the user fix their schema or transform, the error will happen non-stop.