Add ReplaceStringProcessor for simple string substitution that doesn't involve regex

[dinujoh]

Add ReplaceStringProcessor for simple string substitution that doesn't involve regex

Description

Add ReplaceStringProcessor for simple string substitution that doesn't involve regex. It uses java String.replace() method that is highly optimized for simple string replacements

Issues Resolved

Resolves #4953

Check List

• New functionality includes testing.
• New functionality has a documentation issue. Please link to it in this PR.
  • New functionality has javadoc added
• Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[dlvenable]

This is a nice improvement for pipeline authors to perform new mutations.

Thank you for using EventKey.

[oeyh]

The changes look good!

I wonder if we should merge this into the existing substitute_string processor as a different method. Something like this:

    - substitute_string:
        entries:
          - source: "message"
            from: "ab"
            to: "ef"
            method: "simple"  # default is "regex" for existing replace using regex matcher

[oeyh]

Should we call it replace_when here?

[dinujoh]

good catch

[dlvenable]

The changes look good!

I wonder if we should merge this into the existing substitute_string processor as a different method. Something like this:

    - substitute_string:
        entries:
          - source: "message"
            from: "ab"
            to: "ef"
            method: "simple"  # default is "regex" for existing replace using regex matcher

So if I follow you, maybe we don't need a new processor here? Just an option?

[dinujoh]

The changes look good!

I wonder if we should merge this into the existing substitute_string processor as a different method. Something like this:

    - substitute_string:
        entries:
          - source: "message"
            from: "ab"
            to: "ef"
            method: "simple"  # default is "regex" for existing replace using regex matcher

Keeping them decoupled will help with simplicity.

[oeyh]

So if I follow you, maybe we don't need a new processor here? Just an option?

Yes. That's the idea. It reduces duplicate code and is more extensible if we ever add other string replace methods in the future. But I'm OK with the new processor added here as well.