nm tool in Boot2Qt toolchains on Windows hosts fails on symlink

Steps to reproduce (works with other paths and other B2Q variants and versions as well):

• Install basic Qt via online installer in C:\Qt
• Install BSP from meta-b2qt-embedded-qbsp-x86_64-mingw32-raspberrypi4-64-6.2.4.qbsp
• Open commandline prompt and try the following
• Enter the cross-compile environment call C:\Qt\6.2.4\Boot2Qt\raspberrypi4-64\toolchain\environment-setup-cortexa72-poky-linux.bat
• Try to list QtCore symbols with nm on a symlink: %NM% -D -P C:/Qt/6211B8~1.4/Boot2Qt/RASPBE~1/TOOLCH~1/sysroots/cortexa72-poky-linux/usr/lib/libQt6Core.so.6
• Try to list QtCore symbols with nm on the real file: %NM% -D -P C:/Qt/6211B8~1.4/Boot2Qt/RASPBE~1/TOOLCH~1/sysroots/cortexa72-poky-linux/usr/lib/libQt6Core.so.6.2.4

The first NM call does not generate any output at all but also no error.
The second NM call works as expected.

This behavior becomes an issue when building Squish for embedded devices on a Windows host.
Squish configure uses the NM tool to locate exported symbols in Qt and it does that via the .so.6 suffixed library.