Bumps [org.assertj:assertj-core](https://github.com/assertj/assertj) from 3.27.4 to 3.27.5.
- [Release notes](https://github.com/assertj/assertj/releases)
- [Commits](assertj/assertj@assertj-build-3.27.4...assertj-build-3.27.5)

---
updated-dependencies:
- dependency-name: org.assertj:assertj-core
  dependency-version: 3.27.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

Bumps [org.assertj:assertj-core](https://github.com/assertj/assertj) from 3.27.5 to 3.27.6.
- [Release notes](https://github.com/assertj/assertj/releases)
- [Commits](assertj/assertj@assertj-build-3.27.5...assertj-build-3.27.6)

---
updated-dependencies:
- dependency-name: org.assertj:assertj-core
  dependency-version: 3.27.6
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

Bumps [com.github.luben:zstd-jni](https://github.com/luben/zstd-jni) from 1.5.7-4 to 1.5.7-5.
- [Commits](luben/zstd-jni@v1.5.7-4...v1.5.7-5)

---
updated-dependencies:
- dependency-name: com.github.luben:zstd-jni
  dependency-version: 1.5.7-5
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

…uilds (#390)

* Reduce heap usage threshold from 100MB to 10MB in ConcurrentJarCreator

The previous threshold of 100000000 (100MB) divided by number of threads was causing
OutOfMemoryError issues when creating zip archives, particularly in environments with
limited heap space like CI systems. The ByteArrayOutputStream used internally can grow
up to 2x the threshold before switching to disk-based storage, leading to excessive
memory consumption.

Reducing to 10000000 (10MB) reduces memory pressure while still maintaining reasonable
performance. For typical builds with 4 threads, this means:
- Before: 25MB per stream (potentially 50MB+ with buffer doubling)
- After: 2.5MB per stream (potentially 5MB+ with buffer doubling)

This change addresses the heap space errors reported in apache/maven CI builds.

Co-authored-by: slachiewicz <[email protected]>

* Add maximum buffer size cap to ByteArrayOutputStream

Cap individual buffer allocations to 16MB to prevent excessive memory usage.
The previous implementation allowed buffers to double indefinitely, which could
lead to very large single allocations (32MB, 64MB, 128MB, etc.) that contribute
to heap exhaustion.

With this cap, when more than 16MB of data needs to be stored, the
ByteArrayOutputStream will create multiple 16MB buffers instead of one giant
buffer. This spreads the memory allocation across multiple smaller chunks
and prevents heap fragmentation issues.

Combined with the reduced threshold in ConcurrentJarCreator, this provides
defense-in-depth against OutOfMemoryError during zip archive creation.

Co-authored-by: slachiewicz <[email protected]>

---------

Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: slachiewicz <[email protected]>

…ed archivers (#392)

* Override getFiles() in AbstractZipArchiver to normalize paths to forward slashes

Co-authored-by: slachiewicz <[email protected]>

---------
Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: slachiewicz <[email protected]>

Co-authored-by: Copilot <[email protected]>