[NativeAOT] rationalize #includes in the native runtime

[VSadov]

The native runtime has a complicated past. Base implementations had different plans about layering. Some things got stitched together from working pieces when productized. Although things work, it could be incrementally a nuisance to move forward.

• Ideally #include would be about functionality a file wants to use directly. Indirect dependencies should be included implicitly.
• Ideally there should be no sensitivity to the order of includes.

There are always exceptions from these rules, but there must be reasons.

[ghost]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The native runtime had a complicated past. Some things are stitched together from working pieces and though things work, it could be incrementally difficult to move forward.

• Ideally #include would be about functionality a file wants to use directly. Indirect dependencies should be included implicitly.
• Ideally there should be no sensitivity to the order of includes.

There are always exceptions from these rules, but there must be reasons.

Author:	VSadov
Assignees:	-
Labels:	untriaged, area-NativeAOT-coreclr
Milestone:	-