NIFI-14678 Aligned the JoltTransformJSON tags with the Jolt DSL names.

[dan-s1]

Summary

NIFI-14678

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 suggesting these additional tags @dan-s1.

In this case, I don't think it is necessary or helpful to include every Jolt operation as a tag. Tags can be used for various purposes, for documentation and feature discovery, but enumerating all possible options starts to go beyond general usage.

However, following from your question in the Jira issue, I do agree that it would be better to align the tags with the DSL names from the Jolt documentation, so repurposing this Jira and pull request to align the tags with those DSL names (shift instead of shiftr), would be helpful.