[8.17](backport #42218) [filebeat][streaming] - Added more retry codes to websocket retry logic

[mergify]

Type of change

• Bug

Proposed commit message

Some valid websocket retry codes were missing from the initial implementation, which could lead to retries not occurring in some scenarios, hence added some more codes to retry on. There is a table below that shows what codes are currently retryable and why.

Table Of Reasons

+---------------------------------------+---------------------------------------------------------+---------+
| Close Code                            | Description                                             | Retry?  |
+---------------------------------------+---------------------------------------------------------+---------+
| 1000 - CloseNormalClosure             | Connection closed normally.(can be a false positive)    | Yes     |
| 1001 - CloseGoingAway                 | Endpoint is going away (e.g., server shutdown).         | Yes     |
| 1002 - CloseProtocolError             | Protocol error (e.g., malformed frames).                | No      |
| 1003 - CloseUnsupportedData           | Unsupported data type received.                         | No      |
| 1005 - CloseNoStatusReceived          | No status code provided (abnormal closure).             | Yes     |
| 1006 - CloseAbnormalClosure           | Abnormal connection closure (unexpected).               | Yes     |
| 1007 - CloseInvalidFramePayloadData   | Invalid payload data (e.g., bad UTF-8).                 | No      |
| 1008 - ClosePolicyViolation           | Policy violation (e.g., authentication issues).         | No      |
| 1009 - CloseMessageTooBig             | Received message exceeds allowed size.                  | Yes     |
| 1010 - CloseMandatoryExtension        | Required extensions not supported.                      | No      |
| 1011 - CloseInternalServerErr         | Server encountered an unexpected error.                 | Yes     |
| 1012 - CloseServiceRestart            | Server is restarting.                                   | Yes     |
| 1013 - CloseTryAgainLater             | Server is overloaded; try again later.                  | Yes     |
| 1015 - CloseTLSHandshake              | TLS handshake failure (e.g., certificate issues).       | Yes     |
+---------------------------------------+---------------------------------------------------------+---------+

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.

Disruptive User Impact

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Relates [proofpoint_on_demand]: Datastreams do not recover after websocket error integrations#11816

Use cases

Screenshots

Logs

---

This is an automatic backport of pull request #42218 done by [Mergify](https://mergify.com).

[botelastic]

This pull request doesn't have a Team:<team> label.