0.2.1 — the image on Python 3.14

A patch release for the image. Nothing in the package itself changed, and
nothing new is enabled: the policy file remains the only thing that decides
which tools exist.

The published image runs Python 3.14

The newest version this package supports and is tested against, up from 3.13.
It reaches whoever pulls the image. An installation from the package index is
unaffected and keeps running on whatever Python it is installed into, 3.11 or
newer.

The tags a user pulls are derived from this release tag, so the base image
moves only when a version number is spent on it.

Pinning, now written down

The registry has carried a minor-line tag since the first image and nothing
said so. All four of these exist:

docker pull ghcr.io/benethos-hub/lexware-office-mcp:0.2.1   # one release
docker pull ghcr.io/benethos-hub/lexware-office-mcp:0.2     # follows its patches
docker pull ghcr.io/benethos-hub/lexware-office-mcp:latest  # moves every release
docker pull ghcr.io/benethos-hub/lexware-office-mcp:edge    # built on demand, not a release

Pin one of the first two for anything you depend on. The README and
compose.yaml say the same beside the line where the tag is actually typed.

Also

Locked development dependencies refreshed - ruff 0.16.3 to 0.16.4, which
reaches the development environment and CI only.

Upgrading from 0.2.0 is a pull or a reinstall. No setting, tool, argument
or output changed.