NIFI-15636 - Fix NPE in StandardFlowComparator when property descriptors are null in compareProperties

[pvillard31]

Summary

NIFI-15636 - Fix NPE in StandardFlowComparator when property descriptors are null in compareProperties

The compare(VersionedFlowRegistryClient) method already wraps its compareProperties call with the existing nullToEmpty() helper, but the same protection is missing from the compare methods for VersionedProcessor, VersionedReportingTask, VersionedFlowAnalysisRule, VersionedParameterProvider, and VersionedControllerService.

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 contains commits signed with a registered key indicating Verified status

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 ./mvnw clean install -P contrib-check
  • JDK 21
  • JDK 25

Licensing

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

Documentation

• Documentation formatting appears as expected in rendered files

[exceptionfactory]

Thanks @pvillard31, although this sounds like it should not happen under most circumstances, the null safety is help and straightforward. +1 merging