Adding filenames from the zip to the response for httpjson

[kgeller]

What does this PR do?

The httpjson input will report filenames for application/zip events in the response.

Why is it important?

We have a bug for an integration that utilizes the filename to determine a log_type field as the field is in the name. For example, filename="delivery_20160705162902600.log" -> log_type: delivery. When utilizing compress: true, the filename is instead a random guid and so the log_type can't be derived, example filename="8578FCFC-A305-4D9A-99CB-F4D5ECEFE297.zip".

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Closes #33952

Use cases

Screenshots

Logs

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @kgeller? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-12-15T15:31:57.248+0000

• Duration: 75 min 41 sec

Test stats 🧪

Test	Results
Failed	0
Passed	2532
Skipped	167
Total	2699

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)