`analytics_test.dart` failing on the Flutter customer test registry

Example failure:

```
00:04 +33 -1: /b/s/w/ir/x/t/flutter_customer_testing.flutter_devtools.TYUQGO/tests/packages/devtools_app/test/shared/analytics/analytics_test.dart: createStackTraceForAnalytics for stack trace with DevTools stack frames near the top [E]
| Expected: '/b/s/w/ir/x/w/rc/tmp6qd7qvz0/hosted/pub.dev/vm_service-14.3.0/lib/src/vm_service.dart 95:18 | 28240\n'
| '/b/s/w/ir/x/w/rc/tmp6qd7qvz0/hosted/pub.dev/vm_service-14.3.0/lib/src/dart_io_extensions.dart 63:12 | 28301\n'
| '/b/s/w/ir/x/w/rc/tmp6qd7qvz0/hosted/pub.dev/vm_service-14.3.0/lib/src/dart_io_extensions.dart 61:25 | 28300\n'
| '/b/s/w/ir/x/w/devtools/packages/devtools_app/lib/src/screens/network/network_service.dart 104:34 | 28297\n'
| '/b/s/w/ir/x/w/devtools/packages/devtools_app_shared/lib/src/service/service_utils.dart 82:25 | 9696\n'
| 'org-dartlang-sdk:///dart-sdk/lib/_internal/wasm/lib/async_patch.dart 103:30 | 2140'
| Actual: '../../../../../w/rc/tmp6qd7qvz0/hosted/pub.dev/vm_service-14.3.0/lib/src/vm_service.dart 95:18 | 28240\n'
| '../../../../../w/rc/tmp6qd7qvz0/hosted/pub.dev/vm_service-14.3.0/lib/src/dart_io_extensions.dart 63:12 | 28301\n'
| '../../../../../w/rc/tmp6qd7qvz0/hosted/pub.dev/vm_service-14.3.0/lib/src/dart_io_extensions.dart 61:25 | 28300\n'
| '../../../../../w/devtools/packages/devtools_app/lib/src/screens/network/network_service.dart 104:34 | 28297\n'
| '../../../../../w/devtools/packages/devtools_app_shared/lib/src/service/service_utils.dart 82:25 | 9696\n'
| 'org-dartlang-sdk:///dart-sdk/lib/_internal/wasm/lib/async_patch.dart 103:30 | 2140'
| Which: is different.
| Expected: /b/s/w/ir/ ...
| Actual: ../../../. ...
| ^
| Differ at offset 0
|
| package:matcher expect
| test/shared/analytics/analytics_test.dart 21:7 main..
```

Something must be different with how `Trace.parse` is behaving in the DevTools CI test environment and the Flutter Customer Test environment.

The devtools customer tests were disabled in https://github.com/flutter/tests/pull/442.

Beginne mit packages/devtools_app/test/shared/analytics/analytics_test.dart und dem von createStackTraceForAnalytics verwendeten Verhalten von Trace.parse; vergleiche den fehlschlagenden Test in DevTools CI und der Flutter Customer Test-Umgebung. Als abgeschlossen gilt die Aufgabe, wenn der Test in der Kunden-Registry mit der erwarteten Formatierung des Stack-Trace-Pfads erfolgreich ist, sodass die deaktivierten Kundentests erneut geprüft werden können.

Vom Indexierungsmodell aus dem Issue-Text verfasst.