Enhance DAPR Pulsar pub/sub component to enable message compression

[jslatten]

Description

Added enhancement to enable compression in Pulsar pub/sub component.

Issue reference

We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #4147

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• [ X] Created/updated tests
• [X ] Extended the documentation
  • [X ] Created the dapr/docs PR: Add new documentation to enable Pulsar PubSub message compression docs#4990

Note: We expect contributors to open a corresponding documentation PR in the dapr/docs repository. As the implementer, you are the best person to document your work! Implementation PRs will not be merged until the documentation PR is opened and ready for review.

[Copilot]

Pull request overview

This PR enhances the DAPR Pulsar pub/sub component by adding message compression support, allowing users to configure compression type (none, lz4, zlib, zstd) and compression level (default, faster, better) for published messages.

• Adds two new metadata fields: compressionType and compressionLevel
• Implements parsing and validation functions following existing code patterns
• Provides comprehensive test coverage for the new functionality

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
pubsub/pulsar/metadata.go	Adds CompressionType and CompressionLevel fields to pulsarMetadata struct
pubsub/pulsar/pulsar.go	Implements compression configuration parsing, validation, and integration into producer options
pubsub/pulsar/pulsar_test.go	Adds comprehensive tests for compression type, level, and their combinations

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[jslatten]

@yaron2 The merge seems to be blocked by a failed test with an unrelated component code (Kafka). Can someone please check whether the workflow or test is actually functioning as expected?

[yaron2]

@yaron2 The merge seems to be blocked by a failed test with an unrelated component code (Kafka). Can someone please check whether the workflow or test is actually functioning as expected?

All checks pass now

[jslatten]

@yaron2 Thank you!

[sicoyle]

LGTM - thank you!