Fix windows tests

[mwm126]

• I agree to follow the project's code of conduct.
• I added an entry to CHANGES.md if knowledge of this change could be valuable to users.

---

[metasim]

I'm not actually able to test on a Windows computer, so my review is only source-level. 😄

[mwm126]

Implemented fixes. I can't test on Windows at the moment, but I can test tomorrow.
Hopefully PR 218 can then be merged!

[pka]

#218 disables all broken tests, so it did run fine back then.

[mwm126]

The issues with /tmp/ on Windows are resolved, but I was also getting an error:

---- vector::vector_tests::tests::test_write_features stdout ----
thread 'vector::vector_tests::tests::test_write_features' panicked at 'called `Result::unwrap()`
on an `Err` value: Os { code: 32, kind: Uncategorized,
message: "The process cannot access the file because it is being used by another process." }',
 src\vector\vector_tests\mod.rs:793:53
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

My solution was to put the open ds: Dataset in it's own scope so that it's closed before being removed (to tidy up after the test), which results in all tests passing on Windows (for me).

[metasim]

bors r+

[bors]

Build succeeded:

• ci gdal-32
• ci gdal-32 (--all-features)
• ci gdal-33
• ci gdal-33 (--all-features)
• ci gdal-34
• ci gdal-34 (--all-features)
• ci gdal-35
• ci gdal-35 (--all-features)
• ci ubuntu-lts
• ci ubuntu-lts (--all-features)