chore: bump dependencies

[nyurik]

Update many dependencies, and fix up the code to match the changes.

• I agree to follow the project's code of conduct.
• I added an entry to the project's change log file if knowledge of this change could be valuable to users.
  • Usually called CHANGES.md or CHANGELOG.md
  • Prefix changelog entries for breaking changes with "BREAKING: "

---

[Copilot]

Pull Request Overview

A chore PR to bump various dependencies and align code with updated APIs.

• Refactored wkt_reader.rs to use new wkt methods (coord, points, line_strings, etc.) instead of tuple fields.
• Updated benchmarking imports (black_box) and bumped criterion, dbase, gdal, geo, gpx, and wkt versions in Cargo.toml.
• Added a new ## Dependencies section in README.md with system package install instructions.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
geozero/src/wkt/wkt_reader.rs	Replaced direct tuple access (e.g., g.0) with new wkt crate methods for geometry
geozero-bench/benches/mvtbench.rs	Moved black_box import to std::hint per Criterion 0.6
README.md	Added ## Dependencies section with apt-get instructions
Cargo.toml	Bumped versions of several crates (criterion, dbase, gdal, geo, gpx, wkt)

Comments suppressed due to low confidence (3)

geozero/src/wkt/wkt_reader.rs:113

• [nitpick] Consider reusing the outer multi_dim variable here or renaming multi_dim1 to a more descriptive name (e.g., inner_multi_dim) to improve readability.

let multi_dim1 = processor.multi_dim();

README.md:263

• [nitpick] Consider adding installation instructions for macOS (e.g., brew install geos gdal) and other common platforms to help users on non-Linux systems.

## Dependencies

[michaelkirk]

LGTM, thanks!

[nyurik]

@michaelkirk i also bumped edition to 2024 because now dependencies won't compile without support for that, so makes sense to migrate as well.

[michaelkirk]

Oh yeah, I didn't see the 2024 update.

In georust/geo we have a minimum 6 months support window, but I don't feel strongly about requiring that here, so I'm OK with merging it if @pka is.

[nyurik]

@michaelkirk I did not update it initially, but there was no point to keep it back because multiple non-optional dependencies were requiring it - so it's basically either that or we would have to postpone this update 🤷