Update supported-configurations.json (#11184)

# What Does This Do
Recent changes in the `validate_supported_configurations_v2_local_file`
have led to strict matching data in the local file and the registry.
This uncovered multiple incorrect entries in the local file in
dd-trace-java. This PR updates the file to be accurate with what is
actually being stored in the tracer.
# Motivation

# Additional Notes

# Contributor Checklist

- Format the title according to [the contribution
guidelines](https://github.com/DataDog/dd-trace-java/blob/master/CONTRIBUTING.md#title-format)
- Assign the `type:` and (`comp:` or `inst:`) labels in addition to [any
other useful
labels](https://github.com/DataDog/dd-trace-java/blob/master/CONTRIBUTING.md#labels)
- Avoid using `close`, `fix`, or [any linking
keywords](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)
when referencing an issue
Use `solves` instead, and assign the PR
[milestone](https://github.com/DataDog/dd-trace-java/milestones) to the
issue
- Update the
[CODEOWNERS](https://github.com/DataDog/dd-trace-java/blob/master/.github/CODEOWNERS)
file on source file addition, migration, or deletion
- Update [public
documentation](https://docs.datadoghq.com/tracing/trace_collection/library_config/java/)
with any new configuration flags or behaviors

Jira ticket: [PROJ-IDENT]

***Note:*** **Once your PR is ready to merge, add it to the merge queue
by commenting `/merge`.** `/merge -c` cancels the queue request. `/merge
-f --reason "reason"` skips all merge queue checks; please use this
judiciously, as some checks do not run at the PR-level. For more
information, see [this
doc](https://datadoghq.atlassian.net/wiki/spaces/DEVX/pages/3121612126/MergeQueue).

<!--
# Opening vs Drafting a PR:
When opening a pull request, please open it as a draft to not auto
assign reviewers before you feel the pull request is in a reviewable
state.

# Linking a JIRA ticket:
Please link your JIRA ticket by adding its identifier between brackets
(ex [PROJ-IDENT]) in the PR description, not the title.
This requirement only applies to Datadog employees.
-->

Author: mhlidd

metadata/supported-configurations.json

@@ -909,7 +909,7 @@
       {
         "version": "A",
         "type": "boolean",
-        "default": "true",
+        "default": "false",
         "aliases": []
       }
     ],
@@ -1107,7 +1107,7 @@
     ],
     "DD_DATA_STREAMS_TRANSACTION_EXTRACTORS": [
       {
-        "version": "A",
+        "version": "B",
         "type": "string",
         "default": null,
         "aliases": []
@@ -2227,7 +2227,7 @@
     ],
     "DD_TRACE_LOG_LEVEL": [
       {
-        "version": "A",
+        "version": "D",
         "type": "string",
         "default": null,
         "aliases": ["DD_LOG_LEVEL"]
@@ -2371,23 +2371,23 @@
     ],
     "DD_OTLP_TRACES_ENDPOINT": [
       {
-        "version": "A",
+        "version": "B",
         "type": "string",
         "default": null,
         "aliases": []
       }
     ],
     "DD_OTLP_TRACES_HEADERS": [
       {
-        "version": "A",
+        "version": "B",
         "type": "map",
         "default": null,
         "aliases": []
       }
     ],
     "DD_OTLP_TRACES_PROTOCOL": [
       {
-        "version": "A",
+        "version": "B",
         "type": "string",
         "default": "HTTP_PROTOBUF",
         "aliases": []
@@ -11115,7 +11115,7 @@
     ],
     "DD_TRACE_WEBSOCKET_ENABLED": [
       {
-        "version": "B",
+        "version": "C",
         "type": "boolean",
         "default": "true",
         "aliases": ["DD_TRACE_INTEGRATION_WEBSOCKET_ENABLED", "DD_INTEGRATION_WEBSOCKET_ENABLED"]