[docs] Medium-weight GC profiling option in Profiler API

[mjsabby]

Creating an issue based on the discussion in dotnet/coreclr#22866

There are currently two profiling modes checked in to .NET Core:

(1) Full GC Profiling - Expensive but exhaustive
(2) Basic GC Profiling - Very efficient but somewhat lacking for some types of analysis

This issue is there to introduce a third mode which is somewhere in between the Full and Basic.

The goal of this middle ground mode is to provide everything basic profiling provides and the most important aspect of the full profiling capability which is the ability to track objects after a GC moves them.

In fact, coupled with an additional Profiler API (https://github.com/dotnet/coreclr/issues/24155), the Full GC profiling capability can be emulated by the profiler if it is so chooses at the cost of additional complexity on the profiler side.

Summarily, this mode will enable the MovedReferences2 profiler callback to be called for compacting garbage collections, but skip SurvivedReferences2 for non-compatcing garbage collections.

[mjsabby]

cc @Maoni0

[tommcdon]

@mjsabby are you interested in doing this work for 3.0?
cc @noahfalk @davmason

[mjsabby]

@tommcdon yeah, I already did so I’ll close this.

[tommcdon]

@mjsabby thanks!

[noahfalk]

I'm re-opening this issue until docs are in place.

[tommcdon]

@mjsabby just a kind reminder to add the appropriate documentation for this feature

[ghost]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.