NIFI-3965 adding Hexdump processor to standard bundle

[grebtsew]

Description of : Adding Hexdump processor to standard bundle

Fixes bug/feature NIFI-3965.

Adds Hexdump processor to the nifi standard processor bundle.
The purpose of this processor is to create hexdumps of arbitrary flowfiles and send them as output flowfiles or/and custom attribute.

Processor Properties include:
Mode : Selectable Mode, describing if the converted Hexdump data should yield FlowFile data, Attribute or Both.

Flowfile offset : Non negative integer offset of Hexdump in FlowFile output. If offset is out of bounds no data will be transferred. This is only used if mode is FLOWFILE or BOTH.

Flowfile length : Non negative integer describing maximum size of Hexdump in FlowFile output. 0 = unlimited. This is only used if Mode is FLOWFILE or BOTH.

Attribute name : String Hexdump output attribute name. This is only used if mode is ATTRIBUTE or BOTH.

Attribute offset : Non negative integer offset of attribute Hexdump. If offset is out of bounds no data will be transferred. This is only used if mode is ATTRIBUTE or BOTH.

Attribute length : Non negative integer maximum size of attribute Hexdump. This is only used if mode is ATTRIBUTE or BOTH.

Adds 2 files:
HexDump.java
TestHexDump.java

Edits 1 file:
nifi/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/resources/META-INF/services/org.apache.nifi.processor.Processor

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

• Is there a JIRA ticket associated with this PR? Is it referenced
  in the commit message?

• Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

• Has your PR been rebased against the latest commit within the target branch (typically main)?

• Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

• Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
• Have you written or updated unit tests to verify your changes?
• Have you verified that the full build is successful on JDK 8?
• Have you verified that the full build is successful on JDK 11?
• If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
• If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
• If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
• If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

• Have you ensured that format looks appropriate for the output in which it is rendered?

Note:

Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

[github-actions]

We're marking this PR as stale due to lack of updates in the past few months. If after another couple of weeks the stale label has not been removed this PR will be closed. This stale marker and eventual auto close does not indicate a judgement of the PR just lack of reviewer bandwidth and helps us keep the PR queue more manageable. If you would like this PR re-opened you can do so and a committer can remove the stale tag. Or you can open a new PR. Try to help review other PRs to increase PR review bandwidth which in turn helps yours.