Fix default version string format

[scc-tw]

Summary

Fixes #49.

WindowsResource::new() currently initializes the string-table FileVersion and ProductVersion from CARGO_PKG_VERSION, while the fixed FILEVERSION and PRODUCTVERSION values are generated as Windows four-part versions.

For a Cargo version like 1.7.5, that produces:

FILEVERSION 1, 7, 5, 0
PRODUCTVERSION 1, 7, 5, 0
VALUE "FileVersion", "1.7.5"
VALUE "ProductVersion", "1.7.5"

Windows Shell can then report System.FileVersion as 1.7.5.0 but System.Software.ProductVersion as 1.7.5.

This change derives the default string-table versions from the same fixed version value, so the defaults are consistent (1.7.5.0). Explicit user overrides through .set("FileVersion", ...) or .set("ProductVersion", ...) are still honored.

Testing

cargo fmt
cargo test

[BenjaminRi]

Thank you for your contribution. I've let the CI run and it looks good. However, I am not quite certain if this is actually an issue and if we should really fix it?

Windows Shell can then report System.FileVersion as 1.7.5.0 but System.Software.ProductVersion as 1.7.5.

There is no rule against this. It seems like even Microsoft themselves do this and it's a perfectly fine practice.

Could you elaborate if you ran into any issues regarding this discrepancy, or if this is purely aesthetic?