cloudflare_logpush.gateway_http: Fix duplicate key number_of_workers

[kcreddy]

Proposed commit message

#13346 introduced a bug inside gateway_http data stream which allows 
input config to have a duplicate of number_of_workers since it was not
removed from the S3 options logic.

Fix this by removing number_of_workers dependency on S3 bucket collection 
being enabled, similar to other data streams in #13346.

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.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Screenshots

Before

After

[elasticmachine]

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

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: a5b855c

cc @kcreddy

[efd6]

Can you clarify the commit message? Suggest something like

#13346 introduced a bug inside gateway_http data stream which allows 
input config to have a duplicate of number_of_workers since it was not
removed from the S3 options logic.

Fix this by removing number_of_workers dependency on S3 bucket collection 
being enabled, similar to other data streams in #13346.

[elastic-vault-github-plugin-prod]

Package cloudflare_logpush - 1.38.3 containing this change is available at https://epr.elastic.co/package/cloudflare_logpush/1.38.3/