feat(windows): add SDIO driver step

[niStee]

What does this PR do

• add a Windows-only Snappy Driver Installer Origin step that auto-detects SDIO, generates scripts for dry-run/interactive/automatic flows, and keeps the console output concise via print_info
• gate the step behind new enable_sdio/sdio_path config knobs, document them in config.example.toml, and ensure the example config keeps risky defaults disabled
• localize new user-facing text, restructure the Windows step module (windows/mod.rs), and wire Step::Sdio into the runner/default Windows step list (including a clearer "Update WSL" label)

Standards checklist

• The PR title is descriptive
• I have read CONTRIBUTING.md
• Optional: I have tested the code myself
• If this PR introduces new user-facing messages they are translated

For new steps

• Optional: Topgrade skips this step where needed
• Optional: The --dry-run option works with this step
• Optional: The --yes option works with this step if it is supported by the underlying command

Testing

• cargo fmt
• cargo clippy
• cargo test
• /home/nils/.venvs/pre-commit/bin/pre-commit run --all-files (from WSL, skipping gitleaks per Windows limitation)
• cargo run -- --dry-run --only sdio --config tmp/sdio_topgrade_config.toml
• cargo run -- --only sdio --config tmp/sdio_topgrade_config.toml
• cargo run -- --yes --only sdio --config tmp/sdio_topgrade_config.toml
• cargo run -- --only sdio --config tmp/sdio_topgrade_config.toml -v
• cargo run -- --yes --only sdio --config tmp/sdio_topgrade_config.toml -v

[niStee]

@GideonBear, please take a look.

[GideonBear]

Hi, sorry for the wait.
Could you send me an example of what it looks like for the step to run? E.g. can you install an outdated driver, run topgrade --only sdio, and show that it updates, and updated the driver, with screenshots or a screencap?
I'm not going to test SDIO myself, but I want to know what the UX would be like.