NIFI-4344: Improve bulletin messages with exception details.

[Lehel44]

Thank you for submitting a contribution to Apache NiFi.

Please provide a short description of the PR here:

Description of PR

• Changed exception message in Connectable task. Component log automatically adds the component name and id to
  the beginning of the log message, don't need to add it manually.
• Added functionality to make chained exceptions displayed nicely in bulletins.

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 submitting this PR @Lehel44. I noted a couple detailed comments, but after reading the Jira issue, it seems like this may require additional work. Formatting changes seem necessary for presentation in the browser, which may require changing the bulletin model.

[Lehel44]

Based on @tpalfy comment I have changed the place of formatting messages to SimpleProcessLogger in order to avoid branching in LoggingRepository. (The exception messages differs based on they are created by the framework or logged directly.)

[tpalfy]

LGTM+1
Merged into main.