fix( gcp_chronicle sink): add content encoding header when compression is enabled

[ChocPanda]

Summary

Set the Content Encoding header when configuring compression on the gcp chronicle sink

Change Type

• Bug fix
• New feature
• Non-functional (chore, refactoring, docs)
• Performance

Is this a breaking change?

• Yes
• No

How did you test this PR?

Test using the config in the issue #22007

Does this PR include user facing changes?

• Yes. Please add a changelog fragment based on our guidelines.
• No. A maintainer will apply the "no-changelog" label to this PR.

Checklist

• Please read our Vector contributor resources.
• If this PR introduces changes Vector dependencies (modifies Cargo.lock), please
  run dd-rust-license-tool write to regenerate the license inventory and commit the changes (if any). More details here.

References

[bits-bot]

All committers have signed the CLA.

[pront]

This looks good to me. I don't have an E2E environment to confirm how adding this header affects downstream GCP. Did you have a chance to see if you get 200 responses with this fix?

[ChocPanda]

This looks good to me. I don't have an E2E environment to confirm how adding this header affects downstream GCP. Did you have a chance to see if you get 200 responses with this fix?

I have got an environment I can test in I'm struggling to get a complete build to test. I'll keep trying

[pront]

Test using the config in the issue #22007

Hi @ChocPanda, what I meant was, can you repeat what you described in the test plan?

Test using the config in the issue https://github.com/vectordotdev/vector/issues/22007

Also, a CI check is failing. Otherwise this is good to go!