2.2.0

2.2.0 - Python 3.14

Publishes xmsgridtrace for Python 3.14 alongside 3.13, and moves the pinned
dependency set to the releases that carry py3.14 binaries. No C++ source
changed in this release and the XmGridTrace API is unchanged - callers do not
need to re-baseline anything.

Wheels are now built for 3.14 on macOS, Linux and Windows. Windows continues
to publish 3.10 as well, for the desktop products.

Dependencies:

• xmscore 7.0.11 -> 7.0.13
• xmsgrid 9.0.10 -> 9.1.1
• xmsinterp 7.0.9 -> 7.0.12
• xmsextractor 10.0.7 -> 10.0.10

These are the minimum versions that publish py3.14 binaries, not simply the
latest. The previous pins publish only 3.10 and 3.13, so a 3.14 build would
resolve no binary at all; upstream rolled 3.14 out in a single wave on the
newest release of each, and the intermediate versions (xmscore 7.0.12,
xmsgrid 9.0.11 and 9.1.0, xmsinterp 7.0.11, xmsextractor 10.0.9) do not carry
it.

Note for anyone resolving xmsgridtrace alongside xmsgrid directly: the xmsgrid
pin crosses a minor version here, 9.0.x to 9.1.x. That is the reason this is a
minor release rather than a patch.

Build and CI:

• generated from xmsconan 2.23.0, up from 2.21.0
• third-party CI actions are pinned to commit SHAs rather than tags, so a
  retargeted upstream tag cannot run in a job holding this repository secrets
• the lint job now installs flake8-tidy-imports, which registers the
  banned-modules option the generated .flake8 sets. Without the plugin flake8
  accepted the osgeo ban and enforced nothing, while reporting the same green
  as a run that had checked it
• fanning macOS and Linux out across two ABIs renames their jobs and uploaded
  artifacts to carry a -py suffix. Anything fetching release assets
  or required status checks by exact name needs updating to match