Try to fix runnable/testprofile.d CI regression on Windows

[kinke]

I think that test started to rather consistently fail on Windows with #16120. Looking at it, I noticed a functional change, so trying to revert that.

[dlang-bot]

Thanks for your pull request and interest in making D better, @kinke! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.
Please verify that your PR follows this checklist:

• My PR is fully covered with tests (you can see the coverage diff by visiting the details link of the codecov check)
• My PR is as minimal as possible (smaller, focused PRs are easier to review than big ones)
• I have provided a detailed rationale explaining my changes
• New or modified functions have Ddoc comments (with Params: and Returns:)

Please see CONTRIBUTING.md for more information.

---

If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment.

Bugzilla references

Your PR doesn't reference any Bugzilla issue.

If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog.

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub run digger -- build "master + dmd#16147"

[kinke]

Nope, it looks like it started later with #16122: https://dev.azure.com/dlanguage/dmd/_build/results?buildId=41131&view=logs&jobId=6775e4b2-0d76-5db7-9bcd-015c7821c824&j=8af2f344-529d-5953-c6e9-e9e8d82c041d&t=007a24f2-5f9f-5584-8be8-7de5c1d9b6f5 is the oldest failing job on branch master I could find so far

[kinke]

Okay, now only reverting #16122, and CI passed. Might have been luck, but I don't think so. ;)

[RazvanN7]

cc @dkorpel

[RazvanN7]

I'm gonna merge this to unclog the PR queue.

[dkorpel]

How do I proceed here? The PR was green when it was merged, and the error is:

core.exception.OutOfMemoryError@src\core\internal\gc\impl\conservative\gc.d(512): Memory allocation failed

Which doesn't follow from the change.

[kinke]

The issue isn't deterministic, but almost every pipeline since then contained at least one Windows job that failed. The test itself doesn't really allocate anything, so looks like some implicit demangling for profiling broke, somehow on Windows only.