Support Isolate Groups across DevTools

As of Dart 2.15, isolates can exist in an [isolate group](https://dart.dev/guides/language/concurrency#performance-and-isolate-groups). Isolates in a group share executable code and memory. We will need to take this into consideration for the Memory screen as well as other parts of DevTools where we currently assume that we are working with a single isolate (CPU profiler, isolate selector). We will likely also need to update the IsolateManager class to know about isolate groups.

Start by tracing IsolateManager and the Memory screen, CPU profiler, and isolate selector, which the issue identifies as assuming a single isolate. Determine how isolate groups affect each entry point and define consistent group-aware behavior across DevTools. Done means these areas support Dart 2.15 isolate groups without relying on a single-isolate assumption.

Rédigé par le modèle d'indexation à partir du texte de l'issue.