Can we copy artefacts for the fanned Windows jobs instead of a private git repo?

As part of diagnosing a disk space issue on the CI server it was brought to my attention that we're using a private git repository hosted on one of our servers for copying the binary output between the windows compilation and test jobs.

This feels to me like unnecessary complexity and I'm wondering whether it would make sense to use the jenkins artefact from the compile job and pull from that directlry into the test jobs instead of going via that git repository. My understanding is that we were doing the same for the arm32 fanned jobs before we switched them over to using the aarch64 hosted systems for those (since there was no reason to fan them in that situation)

Since I'm not aware of the history of why we chose to use a git repo for the binaries, does anyone have the history of the reasoning, or is there a good reason not to consider using the standard jenkins artefact process instead? @joaocgreis @nodejs/build

Start by reviewing the linked Windows compilation and test jobs, focusing on how binary output moves through the private git repository and Jenkins artifacts. Check the issue discussion for the historical reason for the current flow; done means reaching a documented decision on whether Jenkins artifacts can replace the repository and, if approved, completing that migration.