Add CRC validation to Zoom module

[chemamartinez]

What does this PR do?

This pull request adds:

• Update the HTTP endpoint input to avoid using the secret.value as a salt for the CRC procedure. Instead, a new option called crc.secret is added so for each module it can be filled with the proper value.
• Added new options to the Zoom module:
  • crc.enabled: enable the CRC validation
  • crc.secret: the secret token that is used for the CRC validation

More information about this validation is available here.

Changes in the input related to this CRC validation can be found at #35204.

Checklist

• My code follows the style guidelines of this project

Related issues

• Related to Add CRC support to the Zoom integration integrations#6288
• Related to x-pack/filebeat/input/http_endpoint: Add CRC validation for webhooks #35204

[elasticmachine]

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

[P1llus]

We are doing some minor work on the input first before merging this one, as we are adding a separate secret option.

[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: 2023-06-01T12:18:36.048+0000

• Duration: 74 min 38 sec

Test stats 🧪

Test	Results
Failed	0
Passed	7834
Skipped	749
Total	8583

💚 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!)