NIFI-13995 - CLI - Add start, run once and clear state for processors

[pvillard31]

Summary

NIFI-13995 - CLI - Add start, run once and clear state for processors

./bin/cli.sh nifi processor-start -procid 0138c512-0193-1000-dbd7-1891f898e909 -p nifi-cli.properties
Name  : ...
ID    : 0138c512-0193-1000-dbd7-1891f898e909
Type  : ...
Bundle: ...
State : RUNNING

./bin/cli.sh nifi processor-clear-state -procid 0138c512-0193-1000-dbd7-1891f898e909 -p nifi-cli.properties
Name  : ...
ID    : 0138c512-0193-1000-dbd7-1891f898e909
Type  : ...
Bundle: ...
State : STOPPED

.bin/cli.sh nifi processor-start -procid 0138c512-0193-1000-dbd7-1891f898e909 --runonce -p nifi-cli.properties
Name  : ...
ID    : 0138c512-0193-1000-dbd7-1891f898e909
Type  : ...
Bundle: ...
State : RUN_ONCE

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

• 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 for these additional commands @pvillard31. I noted one question regarding run-once as an argument versus as a separate command.

[exceptionfactory]

At the risk of having more commands, what do you think about having a separate run-processor command, instead of having RUN_ONCE as an optional argument to start? It seems like that would align more closely with the REST API behavior.