[Filebeat][CometD] Resolve Retry Error Handling

[kush-elastic]

• Bug

What does this PR do?

Filebeat CometD input is closing input worker in case of client-server connection issue with EOF error.
Current forked bayeux library is sending error message while any connection issues from salesforce side. which in return CometD is assuming it to be un recoverable error and closing the input worker.
This PR contains draft changes for handling above mentioned issue.

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 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.

Related issues

• Relates [Filebeat][CometD] Filebeat CometD input closes Filebeat worker while getting connection or EOF error from bayeux library #34326
• Relates https://github.com/elastic/sdh-beats/issues/2898

Logs

{"log.level":"error","@timestamp":"2023-01-20T16:17:09.542+0530","log.logger":"cometd","log.origin":{"file.name":"cometd/input.go","file.line":46},"message":"got error while running input","service.name":"filebeat","pubsub_channel":"channel_name","error":{"message":"error collecting events: cannot connect to bayeux: bad unrecoverable call: Post "[http://localhost:8080/cometd/38.0](http://localhost:8080/cometd/38.0%5C)": EOF, trying again"},"ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2023-01-20T16:17:09.543+0530","log.logger":"cometd","log.origin":{"file.name":"cometd/input.go","file.line":47},"message":"Input worker has stopped.","service.name":"filebeat","pubsub_channel":"channel_name","ecs.version":"1.6.0"}

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @kush-elastic? 🙏.
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: 2023-02-16T04:35:05.644+0000

• Duration: 73 min 26 sec

Test stats 🧪

Test	Results
Failed	0
Passed	2865
Skipped	172
Total	3037

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

[rdner]

All in all the change looks good to me but I'd like to ask another pair of eyes from someone who knows the area very well.

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b bayeux_changes upstream/bayeux_changes
git merge upstream/main
git push upstream bayeux_changes

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b bayeux_changes upstream/bayeux_changes
git merge upstream/main
git push upstream bayeux_changes

[P1llus]

Unless there is anything more, we should merge @agithomas @rdner @efd6 ?

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b bayeux_changes upstream/bayeux_changes
git merge upstream/main
git push upstream bayeux_changes

[agithomas]

LGTM!