NIFI-15737: Add Sequential evaluation mode to UpdateAttribute Advanced UI

[Scrooge-McDucks]

• Add SEQUENTIAL to FlowFilePolicy enum; rules are evaluated in order and each matching rule's actions are applied immediately so subsequent rules see the updated attributes rather than the original values
• Implement evaluateSequential() in UpdateAttribute: applies basic dynamic properties as the baseline, then evaluates each advanced rule against the progressively updated FlowFile, emitting a single ATTRIBUTES_MODIFIED provenance event listing all matched rules in order
• Write UpdateAttribute.matchedRules attribute to the FlowFile containing all matched rule names comma-separated when running in Sequential mode
• Replace binary Clone/Original slide toggle in the Advanced UI with a three-way button toggle group (Clone / Original / Sequential); Sequential and Original both show the reorder-rules control
• Update additionalDetails.md with Sequential mode description, basic properties interaction, matchedRules attribute, and hotel-bill worked example

Summary

NIFI-15737

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

Screenshots