Fixing the per object hard limit support for regions

[cshung]

Fixes#71790
Fixes#36828

In regions, we can move regions from/to free lists, so just keeping track of the commits for which object-heap during commit/decommit time is no longer enough, we also need to update our accounting when we move them around.

This change created a new bucket for free, that counts the committed memory in the region free lists.

Much of the diff is a refactoring that change the value of total_oh_count from 4 to 3, which is more correct IMO. Many lines were doing -1 which is no longer needed.

The commit-accounting logging statements are intentionally structured so that they can be used to reconstruct the committed region ranges if we have all of them. These can be useful for future tooling purposes (e.g. creating an animated map of how the regions evolves over time)

[ghost]

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

Issue Details

---

Fixes #71790

In regions, we can move regions from/to free lists, so just keeping track of the commits for which object-heap during commit/decommit time is no longer enough, we also need to update our accounting when we move them around.

This change created a new bucket for free, that counts the committed memory in the region free lists.

Much of the diff is a refactoring that change the value of total_oh_count from 4 to 3, which is more correct IMO. Many lines were doing -1 which is no longer needed.

The commit-accounting logging statements are intentionally structured so that they can be used to reconstruct the committed region ranges if we have all of them. These can be useful for future tooling purposes (e.g. creating an animated map of how the regions evolves over time)

Author:	cshung
Assignees:	-
Labels:	area-GC-coreclr
Milestone:	-