Add NoCompression option to tarball compressor

[mdzhigarov]

This PR adds a new NoCompression option to the tarball compressor that allows creating uncompressed tar files instead of gzipped ones.

Changes

• Add NoCompression field to CompressorOptions struct
• Update tarballCompressor to conditionally include -z flag based on NoCompression option
• Add comprehensive unit tests for NoCompression functionality
• Update fake compressor to support new option

Testing

• Tests verify both CompressFilesInDir and CompressSpecificFilesInDir methods
• Tests check for presence/absence of -z flag instead of exact argument matching
• Include end-to-end test comparing compressed vs uncompressed tarball sizes
• All 23 tests pass successfully

Usage

// Create compressed tarball (default behavior)
tarball, err := compressor.CompressFilesInDir(dir, CompressorOptions{})

// Create uncompressed tarball
tarball, err := compressor.CompressFilesInDir(dir, CompressorOptions{NoCompression: true})

Motivation

This feature is useful when you need to create uncompressed tar files, for example when working with already compressed content or when you want to avoid the overhead of compression for small files.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: mdzhigarov / name: Marin Dzhigarov (45b9c17, ffb6efc)

[KauzClay]

I don't have approval powers, but it makes sense to me. Seems to match how CompressorOptions is used in other places in this repo.

Will you then need to pull this into https://github.com/cloudfoundry/bosh-cli/tree/main ?

[mdzhigarov]

I don't have approval powers, but it makes sense to me. Seems to match how CompressorOptions is used in other places in this repo.

Will you then need to pull this into https://github.com/cloudfoundry/bosh-cli/tree/main ?

Yes, that's the plan. I have already prepared the changes in bosh-cli locally. Waiting for this to get merged so that I can open a PR in bosh-cli

[mdzhigarov]

Quite odd... I cannot change the base branch of this PR to get past the check-branch check.
I also tried opening a new PR under cloudfoundry:develop but seems the same check ran again.

Will investigate this tomorrow.
Thanks @rkoster for the review!

[mdzhigarov]

@rkoster Would you please re-trigger the check-branch job and merge this?