[UR] need to use legacy sink on Windows when SYCL_UR_TRACE is active

[cperkinsintel]

Tracked this down when the sycl/test-e2e/Schedulder/HostAccDestruction.cpp test started timing out on some Win machines. UR has the fix, but it wasn't being used when SYCL_UR_TRACE was elected.

[pbalcer]

My preference would be to change the test to work with the new log format. If that's not feasible, you can change the one log entry that is causing issues to use the UR_LOG_LEGACY macro.

[cperkinsintel]

@pbalcer - I may not be quite understanding your comment, and perhaps I should have been clearer in the description.

On Windows, when SYCL_UR_TRACE is used then we sometimes see a SegFault coming from the UR when the app is shutting down. What is happening is UR_LOG inserts a call to a print virtual function that the OS has already cleaned up.
But the UR has an existing fix, it sets and checks the isTearDowned variable to avoid accidentally calling static vars that the OS may have destroyed. That logic is in the legacy sink which but the sink is not used generally, just in a few situations. If someone uses SYCL_UR_TRACE on Windows then it is needed. That's what this PR does it adds another situation where it is used.

I don't work on the UR generally, so I may not be appreciating the full landscape. If there is some OTHER approach instead of the legacy, let me know.

[pbalcer]

The legacy sink was originally added as a way to maintain backward compatibility with the old log format, for tests and tools that relied on parsing it. I wasn't aware it was them co-opted to support this issue with destruction and unload ordering. Setting the legacy sink will, in addition to handling the teardown differently, change the format of the logs. We need to separate these two things.