Annotate APIs throwing PNSE on MacCatalyst

[MaximLipnin]

This is another iteration on work for annotating APIs unsupported on iOS/tvOS - in part of MacCatalyst and it's mostly going to add [UnsupportedOSPlatform("maccatalyst")] to the classes/methods/etc already annotated for iOS/tvOS.

Part of #47910

[dotnet-issue-labeler]

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, to please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

[ghost]

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

Issue Details

---

This is another iteration on work for annotating APIs unsupported on iOS/tvOS - in part of MacCatalyst and it's mostly going to add [UnsupportedOSPlatform("maccatalyst")] to the classes/methods/etc already annotated for iOS/tvOS.

Part of #47910

Author:	MaximLipnin
Assignees:	-
Labels:	area-System.Console, new-api-needs-documentation
Milestone:	-

[marek-safar]

Is it needed if MacCatalyst derives from xamarin.ios

[MaximLipnin]

Is it needed if MacCatalyst derives from xamarin.ios

As far as I can see, the respective GH issue was updated to consider MacCatalyst as well, so perhaps there are some nuances.

[MaximLipnin]

As discussed offline, iOS annotations should be enough to cover MacCatalyst cases, but it needs some validation