os.lstat doesn't properly set st_reparse_tag for junction on a remote NetApp share

Bug report

\\192.168.10.198\vol1\sub is a junction on NetApp share, but in Python 3.10.4 st_reparse_tag is set to 0:

>>> path = "\\\\192.168.10.198\\vol1\\sub"
>>> os.lstat(path).st_reparse_tag
0

>fsutil reparsepoint query \\192.168.10.198\vol1\sub
Reparse Tag Value : 0xa0000003
Tag value: Microsoft
Tag value: Name Surrogate
Tag value: Mount Point
Substitue Name offset: 0
Substitue Name length: 98
Print Name offset:     100
Print Name Length:     98
Substitute Name:       \??\Volume{804BBB02-0000-0000-6270-052200000040}\
Print Name:            \??\Volume{804BBB02-0000-0000-6270-052200000040}\

I checked in the Python code that:

• os.lstat uses GetFileInformationByHandleEx call with FileAttributeTagInfo to get the value of the reparse tag
• DeviceIoControl with FSCTL_GET_REPARSE_POINT, which is also used in Python source code, works fine
• the problem doesn't affect regular remote Windows shares (NTFS filesystem)

Your environment

• CPython versions tested on: 3.10.4
• Operating system and architecture: Windows 2019, NetApp share

先檢查 os.lstat 背後的 Windows 實作，尤其是使用 FileAttributeTagInfo 呼叫 GetFileInformationByHandleEx 的部分。針對 NetApp junction 重現此情況，並將其與使用 FSCTL_GET_REPARSE_POINT 的 DeviceIoControl 進行比較。完成的標準是 st_reparse_tag 回報遠端 junction 的 reparse tag，同時維持對一般 Windows 共用的行為不變。