Feature/nifi integration address text

[QuanticPony]

Proposal to add a property in NiFi-integration processors to allow users to choose address definition strategy and add support for Expression Language in addresses definition.

Issues related:

• roll back configurate dynamic properties #648: As stated, adding a lot of addresses as dynamic properties can be tedious.
• Apache NiFi integration should allow Expression Language #593 (Jira PLC4X-196): Expression Language can be supported easily on addresses definition.

Actual behavior:

Addresses are specified one by one as dynamic properties in the processor and stored in a map when onScheduled method is triggered.
Expression Language is not supported.

Proposed behavior:

Let user decide between 2 strategies to obtain addresses in the processor:

• Properties as addresses (as actual behavior but with Expression Language): 1 address per dynamic property.
• Property "Address Text": a property where all addresses can be specified as field-value pairs in a JSON.

An address map created every time when onTrigger method is called.

[ottobackwards]

Thanks for the contribution!
The issues with expression language for addresses and having multiple addresses in that property were at the time:

• Putting something complicated to write in a text field is poor for the user
• The original didn't use json, but used special character substitution changing the native addresses which was a no-go
• The addresses / returns need to have their PLC types resolved, and if the address could change every call ( which you have to assume if you use expression language ) then it would be good to have some kind of caching so that it wasn't so costly every time, and the original PR did not provide that

In order for this PR to land, it would have to address the caching issue. Having json addresses the "don't invent a custom addressing delimiter" issue. We would just have to live with how poor writing complicated json in that UI would be ( or doing it external and cut and pasting it in)

[QuanticPony]

@ottobackwards regarding the cache:
I have added a cache to store addresses-to-PlcTags and addresses-to-RecordSchema mappings.

I have done some tests and seems to speed up ut to 10x the processors.

At the moment each processor has its cache and a new property: Schema Cache Size with default value 1.

Waiting for feedback

[QuanticPony]

Thank you for your feedback @ottobackwards!
I have made commits addressing all suggested changes

[ottobackwards]

This looks good. If you are ready, I will let you move it from Draft to ready for review, then I'll finish up

[hutcheb]

Just going through and removing jackson being pinned at version 2.14.1, this will result in it being bumped to 2.14.2.

This was causing an issue with the build. Let me know if there was a specific reason this was being held back.

[QuanticPony]

Must be a left over from testing. There is not any reason, sorry for the inconvenience