NIFI-8412: Use proper log messages in PublishKafka(Record) processors

[naddym]

incase of 'Rollback on Failure'

Thank you for submitting a contribution to Apache NiFi.

Please provide a short description of the PR here:

Description of PR

Enables X functionality; fixes bug NIFI-YYYY.

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.

[joewitt]

The changes would be fine and I'd merge except you are now providing the exception data when we had originally not wanted to and are changing the log message such that it isn't making clear the transfer to the 'specified failure relationship'.

For instance you changed
getLogger().error("Failed to send messages to Kafka; will yield Processor and transfer FlowFiles to failure");
To
getLogger().error("Failed to send messages to Kafka; will yield Processor due to {}", e);
Instead lets just do the pattern you had already
getLogger().info("Failed to send FlowFile to kafka; will yield Processor and transfer flowfiles to specified failure strategy");

[naddym]

Thanks @joewitt for clarifying, I was thinking about that but since it's an error logging, so taught it would make sense to also include stacktrace. I have made the changes requested.