### Is your feature request related to a problem? Please describe.

Currently, VisualMagick does not permit to reproduce a Windows build since `CloneRepositories.sh` always retrieves the latest git checkout.

This means that Windows builds that do not always use the latest ImageMagick version break from time to time - the latest example is the `oss-fuzz` directory in ImageMagick.

### Describe the solution you'd like

`CloneRepositories.sh` should use the date of the latest commit in the `ImageMagick-Windows` repository to retrieve the dependencies up to this point in time.

### Describe alternatives you've considered

I do not see any solution at the moment, besides to always build only the latest Windows version.

### Additional context

`magickwand.js` has the option to be built from source - which few Windows users would use - that currently breaks with each new change in the build process.
Reproducible Windows builds
This is a GitHub Issue
repo:ImageMagick
owner:ImageMagick
Title : Reproducible Windows builds
Issue date:

--- start body ---
### Is your feature request related to a problem? Please describe.

Currently, VisualMagick does not permit to reproduce a Windows build since `CloneRepositories.sh` always retrieves the latest git checkout.

This means that Windows builds that do not always use the latest ImageMagick version break from time to time - the latest example is the `oss-fuzz` directory in ImageMagick.

### Describe the solution you'd like

`CloneRepositories.sh` should use the date of the latest commit in the `ImageMagick-Windows` repository to retrieve the dependencies up to this point in time.

### Describe alternatives you've considered

I do not see any solution at the moment, besides to always build only the latest Windows version.

### Additional context

`magickwand.js` has the option to be built from source - which few Windows users would use - that currently breaks with each new change in the build process.
--- end body ---
