Change generation for NonGC objects for debugger

[EgorBo]

It seems that currently we do expose nongc objects to debugger (via EnumerateHeap API - I've checked that locally):

but with two issues:

1. We report them as Gen2 objects
2. We might report them as "dead" if nobody reference them at the time of memory snapshot, although, in fact, they're always there (immortal).

Presumably, this change requires changes on VS side (and external debuggers if they use this API?)

cc @davmason @noahfalk @cshung @hoyosjs

[ghost]

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

Issue Details

---

It seems that currently we do expose nongc objects to debugger (via EnumerateHeap API - I've checked that locally):

but with two issues:

1. We report them as Gen2 objects
2. We might report them as "dead" if nobody reference them at the time of memory snapshot, although, in fact, they're always there (immortal).

Presumably, this change requires changes on VS side (and external debuggers if they use this API?)

cc @davmason @noahfalk @cshung @hoyosjs

Author:	EgorBo
Assignees:	EgorBo
Labels:	area-Diagnostics-coreclr
Milestone:	-

[noahfalk]

For the VS UI it would be more accurate if VS replaced the word "Generations:" with a different term like "Heaps", "Heap Regions", or "Categories". Its in the grey area to call POH or LOH a generation, but hopefully we can avoid implying that NonGC is a generation.

[davmason]

Thanks Egor!