Devtool extension authoring: EvalOnDartLibrary, how to recursively inspect an Object without causing `Sentinel <expired>` due to race conditions?

Hello!

I think I'm missing something with regards to `EvalOnDartLibrary`. I fail to see how it is possible to fully map out an object without ever risking an `` Sentinel or not loosing the ability to inspect private members.

I am aware that one trick is to do (pseudo code):

```dart
final id = eval('globalMap.register()')

try {
final content = eval('globalMap.get("$id").');
} finally {
eval('globalMap.unregister("$id")');
}
```

This prevents the ``. But afaik, prevents reading private members on the inspected object, due to `globalMap` and the private members being defined in different libraries.
(also, this will forcibly trigger late fields ; which can be undesired)

If we instead do:

```dart
final value= eval('')
final content = eval('that.', scope: {'that': value.id});
```

Then we risk that `value` will expire before `content` is resolved.

Is there something I'm missing here? Or do we need a new feature to solve this?

从 EvalOnDartLibrary API 以及 issue 中描述的两种评估模式开始。复现递归检查场景，并比较 Sentinel 过期、私有成员访问和 late 字段行为。完成的条件是有 maintainer 确认的解决方案或范围明确的新能力，并在调查后确定测试或文档。

由索引模型根据 Issue 内容生成。