Consider being more specific about lib versions/platform for binaries

[huonw]

Currently there's i686/freetype.dll, which is Freetype 2.6.1. It may make sense to instead call the file something like freetype-2.6.1.dll to allow multiple versions to be included and ensure that builds can be reproduced in future, similar to crates.io/Cargo.lock (e.g. if someone comes back to code in a year to fix some small bug and Freetype 3.0 has been released, they may not want to spend the time to upgrade from 2.6, so having the same binaries around is helpful).

Also, if there's any plan to include non-windows binaries, it may also make sense to indicate this in some way, e.g. windows/i686/... or i686/windows/... (although, maybe file extensions are enough?).