Address Copilot review comment: regenerate Python coverage

Copilot comment:

Changing this request to `/users/456` creates additional signal names for route-less servers, but their committed coverage was not regenerated. The ASGI snapshot currently contains only `GET /users/123` and its receive/send child findings (`scenarios/http/python/asgi/opentelemetry-asgi/server/data.json:153-179`), and WSGI likewise only contains `GET /users/123` (`scenarios/http/python/wsgi/opentelemetry-wsgi/server/data.json:86-94`). The Python scenario CI reruns every package and rejects coverage diffs, so these snapshots will change when the query request is emitted as `/users/456`. Please regenerate and commit the affected existing server `data.json` files.

Analysis: ASGI and WSGI omit `http.route`, so their span names use each concrete request path. The distinct query path adds `GET /users/456` findings while preserving the findings for the query-free `/users/123` request. Regenerating both scenarios records the additional server and ASGI child-span findings.

Upsides: The committed coverage now matches the shared contract for every route-less server scenario. Python scenario CI no longer finds stale snapshots.

Downsides: The coverage files contain more findings because each concrete user path remains a separate unbounded-cardinality span name until those instrumentations emit `http.route`.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: trask

scenarios/http/python/asgi/opentelemetry-asgi/server/data.json

@@ -178,6 +178,34 @@
         "attribute_key": "asgi.event.type"
       }
     },
+    {
+      "id": "http_route_not_present",
+      "message": "Server span 'GET /users/456' uses target '/users/456' but lacks 'http.route', so the matched route and target cardinality cannot be verified.",
+      "signal_type": "span",
+      "signal_name": "GET /users/456",
+      "context": {
+        "kind": "server",
+        "target": "/users/456"
+      }
+    },
+    {
+      "id": "missing_attribute",
+      "message": "Attribute 'asgi.event.type' does not exist in the registry.",
+      "signal_type": "span",
+      "signal_name": "GET /users/456 http receive",
+      "context": {
+        "attribute_key": "asgi.event.type"
+      }
+    },
+    {
+      "id": "missing_attribute",
+      "message": "Attribute 'asgi.event.type' does not exist in the registry.",
+      "signal_type": "span",
+      "signal_name": "GET /users/456 http send",
+      "context": {
+        "attribute_key": "asgi.event.type"
+      }
+    },
     {
       "id": "http_route_not_present",
       "message": "Server span 'POST /items' uses target '/items' but lacks 'http.route', so the matched route and target cardinality cannot be verified.",

scenarios/http/python/wsgi/opentelemetry-wsgi/server/data.json

@@ -93,6 +93,16 @@
         "target": "/users/123"
       }
     },
+    {
+      "id": "http_route_not_present",
+      "message": "Server span 'GET /users/456' uses target '/users/456' but lacks 'http.route', so the matched route and target cardinality cannot be verified.",
+      "signal_type": "span",
+      "signal_name": "GET /users/456",
+      "context": {
+        "kind": "server",
+        "target": "/users/456"
+      }
+    },
     {
       "id": "http_route_not_present",
       "message": "Server span 'POST /items' uses target '/items' but lacks 'http.route', so the matched route and target cardinality cannot be verified.",