Mention Windows build config ABI incompatibility (backport #7192)

[mergify]

Description

We stopped producing debug Windows binaries some time ago, only leaving release binaries. On Windows, for ABI compatibility, this means anything downstream must also be built in Release or RelWithDebInfo mode. Mention it explicitly here. And mention having to build ROS 2 from source to use another build config.

See: https://discourse.openrobotics.org/t/ros-2-windows-ci-on-github-actions-current-options-and-a-pixi-based-pattern/57736/6

Did you use Generative AI?

No

Additional Information

This should be backported to all distros that only have Windows release binaries, which is all of them, even though we've stopped producing binaries for distros targeting Windows 10, since it is EOL. We can still backport this in case someone is using one of those distros' last Windows binaries.

---

This is an automatic backport of pull request #7192 done by Mergify.

[mergify]

Cherry-pick of 0d14d8e has failed:

On branch mergify/bp/kilted/pr-7192
Your branch is up to date with 'origin/kilted'.

You are currently cherry-picking commit 0d14d8e.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   source/Get-Started/Installation/Windows-Install-Binary.rst

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally