[mono] Clean up internal usage of RuntimeComponents to always be treated as MSBuild Item

[ivanpovazan]

This PR cleans up the internal usage of RuntimeComponents where in some places it is used as a MSBuild Property and in others as an Item, which can lead to unexpected behaviours during app builds for both Android and iOS-like platforms and additionally imposes unnecessary complication of treating them dually in different places.

This PR:

• Removes the possibility of using a wildcard * which previously meant to include all supported components (this was probably the reason to use a Property in the first place).
  • This can be consider a BREAKING CHANGE - however I did not find any internal usage of said feature (I might be wrong though).
• Introduces: UseAllRuntimeComponents MSBuild property which when set to true includes all supported components by parsing the RuntimeComponentManifest.json file and populating RuntimeComponents Item in _InitializeCommonProperties target (in both: AppleBuild.targets and AndroidBuild.targets)
• Cleans up all references of RuntimeComponents to be treated as MSBuild Item
• Simplifies usage of runtime components in various places
• Updating the doc on diagnostic tracing
• Reuses RuntimeComponentManifest.targets for local builds and testing to retrieve available runtime components

---

Follow-up tasks:

• Switch the AndroidSampleApp to use AndroidBuild.targets directly instead of manually inferring build tasks and targets
• Further improve managed debugging of libraries, functional tests and sample applications on both Android and iOS-like platforms

[ghost]

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

Issue Details

---

This PR cleans up the internal usage of RuntimeComponents where in some places it is used as a MSBuild Property and in others as an Item, which can lead to unexpected behaviours during app builds for both Android and iOS-like platforms and additionally imposes unnecessary complication of treating them dually in different places.

This PR:

• Removes the possibility of using a wildcard * which previously meant to include all supported components (this was probably the reason to use a Property in the first place).
  • This can be consider a BREAKING CHANGE - however I did not find any internal usage of said feature (I might be wrong though).
• Introduces: UseAllRuntimeComponents MSBuild property which when set to true includes all supported components by parsing the RuntimeComponentManifest.json file and populating RuntimeComponents Item in _InitializeCommonProperties target (in both: AppleBuild.targets and AndroidBuild.targets)
• Cleans up all references of RuntimeComponents to be treated as MSBuild Item
• Simplifies usage of runtime components in various places
• Updating the doc on diagnostic tracing

---

Follow-up tasks:

• Switch the AndroidSampleApp to use AndroidBuild.targets directly instead of manually inferring build tasks and targets
• Further improve managed debugging of libraries, functional tests and sample applications on both Android and iOS-like platforms

Author:	ivanpovazan
Assignees:	-
Labels:	area-Infrastructure-mono
Milestone:	-

[ivanpovazan]

/cc: @akoeplinger @jandupej @steveisok @kotlarmilos

[jandupej]

This is a welcome simplification. Thanks!

[ivanpovazan]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ivanpovazan]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ivanpovazan]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[steveisok]

LGTM! Thanks for refactoring and making this more straightforward.

[ivanpovazan]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ivanpovazan]

Failures don't seem to be related