add: Strict Mode option to Pipeline configuration

[gregfurman]

Motivation

We need a strict_mode to allow for a processing step to return and log an error, with the subsequent processors not being run.

Related to https://github.com/warpstreamlabs/bento/pull/166 -- where we opted for nacking at the failed processor instead of at the output layer.

Can be used as follows:

pipeline:
  strict_mode: true
  processors:
    - mapping: |
        root = throw(this.value)
    - mapping: |
        root.message = "I'm never reached..."

Changes

• Creates config for a new strict_mode in the pipeline block for.
• Adds a strict processor interface that iterates through all messages from a processor and checks if any contain an error.
• Add wrapper function that, when used, wraps all processors in the above interface.
• Failures will be nacked at the input layer without needing to reach the output.
• Fixes the generate input component always enabling auto_replay_nacks.

TODO

• ~Add more tests.~
• Populate this config at the manager level to allow for nested input.processors and output.processors to also have their results checked for errors.
• Look into adding backoff for retries and shutting off the input to stop new data being read in.
• ~Add documentation for this feature.~