target sdk version support

When making prebuilt binaries you "need" to decide how old of a system you're willing to support. i.e. if you want to rely on APIs introduced in windows 10, your binary won't necessarily work on windows 8.

Currently this is a big *shrug* and I think cargo/rust just uses whatever's available on the machine that built the binary (similar to [target-cpu=native](https://rust-lang.github.io/packed_simd/perf-guide/target-feature/rustflags.html#target-cpu)) that we only address by generating CI that uses the oldest (non-deprecated) Github runners.

Ideally we would help the user here with choosing SDK versions and getting everything setup to do that. Unfortunately this is 100% outside my domain of expertese and I have absolutely no idea how to do this for the 3 big desktop platforms!

The issue names no files, tests, or entry points. Start by researching how Cargo and Rust select target SDK versions for Windows and the other desktop platforms, then inspect the prebuilt-binary and GitHub Actions release configuration. Done should mean users can choose supported SDK versions and get the required setup guidance.

Written by the indexing model from the issue text.