NIFI-13664 allow bundle id to be searchable

[mosermw]

Summary

NIFI-13664

Improved the component Search capability by allowing user to type all or part of a Bundle ID (NAR name) to find matching components. Updated the User Guide.

For example, if you type "nifi-slack" in the Search Bar, it will show "Bundle: nifi-slack-nar" from matching components.

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

• Apache NiFi Jira issue created

Pull Request Tracking

• Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
• Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

• Pull Request based on current revision of the main branch
• Pull Request refers to a feature branch with one commit containing changes

Verification

Please indicate the verification steps performed prior to pull request creation.

Build

• Build completed using mvn clean install -P contrib-check
  • JDK 21

Licensing

• [n/a] New dependencies are compatible with the Apache License 2.0 according to the License Policy
• [n/a] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

• Documentation formatting appears as expected in rendered files

[exceptionfactory]

Thanks @mosermw, the additional search capability looks good! +1 merging

[mosermw]

Thanks for the review @exceptionfactory. May I cherry-pick this into the support/nifi-1.x branch if it merges cleanly?

[exceptionfactory]

Thanks for the review @exceptionfactory. May I cherry-pick this into the support/nifi-1.x branch if it merges cleanly?

You're welcome @mosermw. This commit will not apply to the support branch because the Spring Configuration is now Java-based instead of XML-based, so adding it to the support branch would require a separate PR.

[mosermw]

Thanks for the review @exceptionfactory. May I cherry-pick this into the support/nifi-1.x branch if it merges cleanly?

You're welcome @mosermw. This commit will not apply to the support branch because the Spring Configuration is now Java-based instead of XML-based, so adding it to the support branch would require a separate PR.

Ah, right! The nifi-framework-bundle moved, too. At this point, I don't think a separate PR is worth it.