Adding info to debug WindowsAlternateDataStreamOverwrite failure

[PranavSenthilnathan]

Adding info for: #83659

• Adding assertion on HRESULT in the non-overwrite case to confirm that it does not have the same issue as the WindowsAlternateDataStreamOverwrite
• Adding logging of attributes
• Assertion on contents of files to determine whether everything is written/accessible before copy

I wasn't able to repro this after trying to run nativeaot build on arm64. Confirmed that it wasn't FAT32 issue (tried mounting volume and it gives a different error) and that the tests were running nativeaot (checked PlatformDetection.IsNativeAot). Hopefully adding the above will give some more info next time this fails.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-system-io
See info in area-owners.md if you want to be subscribed.

[adamsitnik]

It's good idea to log more info, I am just not sure if the current implementation is going to work.

[adamsitnik]

LGTM, thank you @PranavSenthilnathan ! If possible please merge it at the beginning of your work day and take a look at the CI in a few hours, just to ensure the changes have not made the CI flaky.