NIFI-11706 Add capability to create dedicated Parameter Contexts for versioned flows when importing

[simonbence]

Summary

NIFI-11706
(Test scenarios helping to understand and review the changes are added as comment on the ticket)

As many Versioned Flows are imported multiple times but used with in somewhat different circumstances (such as: different endpoints, databases, etc.), it would make sense to give the user the possibility to import flows in a way that their Parameter Context become independent from the other instances. In order to achieve this a new checkbox will be added to the Import Version window which makes it possible to decide for the user if she wants to keep the existing Parameter Contexts (bounding the parameters to the potentially existing instances) or she wants to create a new set of Parameter Contexts making the flow parametrised independently.

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 17

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]

Spelling correction:

Suggested change

	class ParameterContextNameCollusionResolverTest {
	class ParameterContextNameCollisionResolverTest {

[exceptionfactory]

Thanks for working on this improvement @simonbence. The general concept makes sense. I noted some spelling issues, and raised a concern about using a boolean versus an enum, which would support future options, and also help clarify the implementation default and optional behavior.

[exceptionfactory]

Thanks for making the adjustments @simonbence, the latest version looks good. +1 merging