Memory debugging are missing lots of features from Observatory

The "Allocation Profile" option on Observatory is, I think, being replaced by "Memory" in devtools.
Right of the bat I am missing details about new and old heap, and internal vs external memory. I seemingly have to download the CSV file to get that info.
Next of I can no longer press any of the classes to get a detailed view (let alone go from there).

I answered something similar in the questionnaire that was given out some time ago (might have been years at this point, I'm not sure), but I'll repeat it here.

When debugging memory issues I often do this:

- Open observatory.
- Go to "Allocation Profile" and find the class. Click it.
- Use one of the "strongly reachable", "all direct instances", "all instances of subclasses" or "all instances of implementors" options.
- Click the resulting list, either going through it by hand (again clicking on the actual instances etc) and/or performing expression evaluations on the list.
- Open two or more instances in a new tab so I can visually compare them by tabbing back-and-forth.
- Use the "Retaining path" and "Inbound references" feature on instances.

Seemingly _none_ of this is possible though devtools. (and if it is I can't find it).

More advanced I've also hacked together scripts that could find interesting instances, I could then print their id and go to observatory for a visual of this instance (and again for instance use the "Retaining path" features etc) by changing the url for another instance (changing the (e.g.) "&objectId=objects%2F6661" part).

Can I please have this functionality back?

/cc @bkonyi @kenzieschmoll

从 DevTools 的 Memory 视图开始，并将其与 Observatory 的 Allocation Profile 进行比较，使用 issue 中关于缺失的堆详细信息、类导航、实例查询、表达式求值、标签页、retaining paths 和传入引用的列表。先检查 CSV 输出以及当前的实例/对象导航。完成的标准是：所请求的内存调试工作流可在 DevTools 中使用，而不需要 Observatory 或 URL 更改。

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