NIFI-9277: Add Record Reader and Writer to ListenHTTP

[Lehel44]

Thank you for submitting a contribution to Apache NiFi.

Please provide a short description of the PR here:

Description of PR

Added record reader and writer to ListenHTTP processor:

• Added new record reading/writing properties to ListenHTTP
• Added validation to ListenHTTP
• Added Record Reader and Writer to ListenHTTPServlet
• In case of using an unpacakger and multipart request the record processing is not used
• Added unit test to TestListenHTTP

JIRA:

https://issues.apache.org/jira/browse/NIFI-9277

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.

[exceptionfactory]

Thanks for this new feature @Lehel44! It seems like the primary value of adding a RecordReader is to provide some amount of input request validation that influences the response sent to the client, but it wasn't clear if that was happening. I noted the catching and logging of exceptions in processRecord().

[tpalfy]

This exception handling seems too broad. MalformedRecordException is probably the only one that should warrant a 400.

[Lehel44]

The IOException here may be thrown by ReaderFactory::createRecordReader or WriterFactory::createRecordWriter or RecordWriter::write. In case of JsonRecordReader this can be a JsonParseException (which is an IOException). I think in case of IOException we might return with 400 (BAD_REQUEST )return code. I separated the SchemaNotFoundException which returns 500 (INTERNAL_SERVER_ERROR).

[tpalfy]

LGTM
Merged into main.