NIFI-15736 Added support of mime type application/x-xz for both compression and decompression in ModifyCompression and for decompression in CompressContent.

[dan-s1]

Summary

NIFI-15736
This PR fixes the ModifyCompression processor to to support mime type application/x-xz for compression and decompression and it fixes the CompressContent processor to support mime type application/x-xz for decompression.

Unit tests were added both for ModifyCompression and CompressContent to demonstrate the support for mime type application/x-xz for both compression and decompression although CompressContent only needed a test for decompression as compression never had an issue. In addition Intellij warnings were fixed in CompressContent unit tests. Lastly, a unit test was added to the ModifyCompression unit tests to demonstrate the expected mapping of mime types to CompressionStrategy in order to demonstrate there was a duplicate entry application/x-lzma that created the bug in the first place

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

[dan-s1]

@pvillard31 @exceptionfactory Do you know why there were only 4 checks run? I thought there are usually at least seven that are usually run.

[ChrisSamo632]

@pvillard31 @exceptionfactory Do you know why there were only 4 checks run? I thought there are usually at least seven that are usually run.

@dan-s1 it depends on which files are changed within the PR, for example the system tests only run if files related to those tests are changed

The action workflows are defined in the .github/workflow folder, where one can see which paths trigger what check (or whether they trigger on PR at all vs. timed cron job)