Allow windows-sys versions >=0.59, <=0.61, delete Cargo.lock

[ColinFinck]

This PR is the result of cargo upgrade --incompatible --pinned --ignore-rust-version --recursive.

In particular, windows-sys 0.61.x consistently uses raw-dylib for importing APIs from Windows DLLs. This makes a huge difference when using non-MSVC toolchains to build Windows binaries, e.g. x86_64-pc-windows-gnullvm.

CC @tesuji

[ColinFinck]

@tesuji: Thanks for quickly having a look! I checked this once more and came to the conclusion that it's better to use the version range ">=0.59, <=0.61" for windows-sys here. This is also what Microsoft recommends in https://crates.io/crates/windows-sys/0.61.2

However, for that to work, I needed to remove the Cargo.lock file. I also added it to .gitignore: Your project is a library and those shouldn't have the Cargo.lock files committed to allow for any compatible dependency version. See https://doc.rust-lang.org/1.71.1/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries

[tesuji]

See https://doc.rust-lang.org/1.71.1/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries

This suggestion was deprecated and removed more than one year ago.

Did >=0.59, <=0.61 make the lock file hard to be resolved?

[tesuji]

Merged in 5ca22fd and published in v1.4.0.

Thank you for your contribution.