WebSocket requests should be captured with transaction type request

[tobiasstadler]

What does this PR do?

WebSocket requests should be captured with transaction type request instead of custom.

Checklist

• This is a bugfix
  • I have updated CHANGELOG.asciidoc
  • I have added tests that would fail without this fix

[github-actions]

👋 @tobiasstadler Thanks a lot for your contribution!

It may take some time before we review a PR, so even if you don’t see activity for some time, it does not mean that we have forgotten about it.

Every once in a while we go through a process of prioritization, after which we are focussing on the tasks that were planned for the upcoming milestone. The prioritization status is typically reflected through the PR labels. It could be pending triage, a candidate for a future milestone, or have a target milestone set to it.

[ghost]

💚 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: 2022-03-18T12:40:15.990+0000

• Duration: 45 min 39 sec

Test stats 🧪

Test	Results
Failed	0
Passed	2744
Skipped	16
Total	2760

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• run benchmark tests : Run the benchmark tests.

• run jdk compatibility tests : Run the JDK Compatibility tests.

• run integration tests : Run the Agent Integration tests.

• run end-to-end tests : Run the APM-ITs.

• run windows tests : Build & tests on windows.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[tobiasstadler]

@felixbarny Would please have a look?

[SylvainJuge]

/test

[tobiasstadler]

@SylvainJuge Could you please restart the tests?

[SylvainJuge]

@elasticmachine run elasticsearch-ci/docs

[tobiasstadler]

Thank You!