Bump version to 0.8.3

[ChiragAgg5k]

The 0.8.3 GitHub release was published without a version bump in the repo, so the Publish workflow (run 28638962896) built mcp_server_appwrite-0.8.2 artifacts and PyPI rejected the upload with 400 Bad Request — 0.8.2 already exists there, and PyPI refuses duplicate filenames.

Bumps pyproject.toml, SERVER_VERSION in constants.py (the appwrite/mcp:0.8.3 Docker image currently self-reports 0.8.2 on /healthz), and uv.lock.

After merging, re-running the failed workflow is not enough — the publish workflow checks out the release tag, which points at the old commit. The 0.8.3 tag and release need to be moved to (or recreated on) the merge commit, which re-triggers publish and should let the PyPI upload succeed.

[greptile-apps]

Greptile Summary

Bumps the package version from 0.8.2 to 0.8.3 across all three version-carrying files, fixing a PyPI publish failure caused by the GitHub release being cut without a prior version bump in the repo.

• pyproject.toml and uv.lock updated so the built sdist/wheel filename matches 0.8.3, avoiding the duplicate-filename rejection from PyPI.
• SERVER_VERSION in constants.py updated so the running Docker image's /healthz endpoint reports the correct version.

Confidence Score: 5/5

Minimal, mechanical version bump with no logic changes — safe to merge.

All three files are updated consistently to 0.8.3, and a repo-wide search confirms no stale 0.8.2 references remain. The change is purely cosmetic metadata with no behavioral impact.

No files require special attention.

Important Files Changed

Filename	Overview
pyproject.toml	Version bumped from 0.8.2 to 0.8.3; no other changes.
src/mcp_server_appwrite/constants.py	SERVER_VERSION constant updated from "0.8.2" to "0.8.3" so the /healthz endpoint will report the correct version.
uv.lock	Lock file updated to reflect the new 0.8.3 package version; no dependency changes.

_{Reviews (1): Last reviewed commit: "(chore): bump version to 0.8.3" | Re-trigger Greptile}