bitdefender: Update doc with input limitation collecting jsonRPC format.

[kcreddy]

Proposed commit message

Update doc with input limitations.

The http_endpoint input limitation on jsonRPC format 
is not properly explained inside the doc, which is confusing to users. 
Update the doc explaining the input limitation on jsonRPC format.

Other changes:
  - Remove comments from pipeline definition.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

Screenshots

Before:

After:

[elasticmachine]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: b33997f

cc @kcreddy

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[efd6]

Thank you for removing those comments.

Note that after 8.14, http_endpoint will be able to handle this kind of POST body since it will be able to evaluate a limited CEL program on the body.

[kcreddy]

Note that after 8.14, http_endpoint will be able to handle this kind of POST body since it will be able to evaluate a limited CEL program on the body.

Created #10020 to support this format.

[elasticmachine]

Package bitdefender - 1.13.0 containing this change is available at https://epr.elastic.co/search?package=bitdefender