Translate Processor: Changed non-exact matching logic

[vishalboin]

Description

Previously when exact option is false, if there is a non-exact match, the target field will be populated with mapped value. This logic has been changed to:
If there is a non-exact match, the mapped value will be replaced in the source value in all occurences and placed in the target field.

For the following config:

  translate - 
    mappings:
      - source: status
        targets:
          - target: result
            regex:
              exact: false
              patterns:
                foo: bar
      - source: status2
        targets:
          - target: result2
            regex:
              exact: false
              patterns:
                foo: bar

Log:

{ 
  "status" : "footer", 
  "status2" : "foofoo"
}

Will be translated to:

{ 
  "status" : "footer", 
  "status2" : "foofoo",
  "result" : "barter", 
  "result2" : "barbar"
}

Issues Resolved

#1914

Check List

• New functionality includes testing.
• New functionality has been documented.
• 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.