This is file 3 of 47 files with nullability disabled in Foundation.

Also, by Copilot:

* Add missing xml comments.
* Improve xml comments with proper formatting and see cref attributes.

Contributes towards #17285.

…Fixes #24043. (#24181)

Since this may result in unintuitive behavior (library projects are
built differently than executable projects, so code that works in an
executable project may not compile when moved to a library project), an
escape hatch was implemented as well.

One unintuitive behavior was when building an executable project with a
library project from Windows: if the library project needs the remote
connection, it would use a different workload, and different remote
connection, than the executable project, which just wouldn't work. So we
don't enable this new behavior when library projects need the remote
connection (which is when bundle resources are precompiled for the
library project; aka when `BundleOriginalResources=false` - note that
it's enabled by default in .NET 10, so developers must opt in to run
into this problem and thus not getting this new behavior).

Fixes #24043.

---------

Co-authored-by: GitHub Copilot <copilot@github.com>
Co-authored-by: GitHub Actions Autoformatter <github-actions-autoformatter@xamarin.com>

…of the 'coremlc' executable. (#24193)

… are stored. Fixes #24052. (#24198)

They're always stored locally.

This fixes an issue when building apps with extensions from Windows.

There are no tests, because there's another issue that breaks building
extensions from Windows (#23516), but the customer validated that the
fix
works for him, and the fix also makes sense.

Fixes #24052.

…ns in known failure strings.

This way we don't have to update the known failures every time we bump the assembly versions.

This is file 4 of 47 files with nullability disabled in Foundation.

Also (by Copilot):

* Improve XML documentation and nullability in NSDirectoryEnumerator.
* Remove placeholder 'To be added.' comments and replace with proper documentation.
* Remove unnecessary whitespace after triple-slash in XML comments.
* Add proper <see cref> attributes for type references.
* Add comprehensive documentation for all IEnumerator implementations.
* Document exception conditions for Reset and Current properties.

Contributes towards #17285.

…CLR. (#24206)

…s enabled. (#24207)

…OS and Mac Catalyst (#24205)

…ith https://ci.dot.net, so update our usage.

…ion of the 'copySceneKitAssets' executable.

Also don't set the PATH or XCODE_DEVELOPER_USR_PATH variables anymore, it's
not needed.

We get suggestions in the doc publishing workflow about 'remarks' in enum
fields (they're ignored), so avoid this by not having 'remarks' in enum
fields.

)

1. This shouldn't ever be necessary.
2. If it were necessary, it should always be necessary.
3. Powershell's exit code handling is 🤯

For reference / amusement / scaring children: https://stackoverflow.com/a/57468523.

We need to use relative paths in learn.microsoft.com links.