build(version): derive app version from git tag when package.json is a placeholder

[PaulHax]

The About box and bug report link read __VERSIONS__.volview, which came straight from package.json. Since main pins the version to 0.0.0 (the release workflow stamps the real version only in the CI checkout), every non-publish build showed 0.0.0.

This keeps package.json at 0.0.0 and instead falls back to git describe --tags in vite.config.ts when the version is the placeholder. When CI has already stamped a real version, that value still wins, so published npm tarballs are unchanged.

Netlify clones shallow and without tags, so git describe had nothing to work with (verified with a --depth 1 clone: describe degrades to a bare sha). The second commit adds a tag fetch to the Netlify build command, tolerant of both shallow and complete repos, and non-fatal if the fetch fails.

Resulting version shown per build:

Build	package.json at build	About box
npm tag release	stamped by CI	tag version
npm dev prerelease	stamped by CI	matches published
Netlify / local	0.0.0	git describe, e.g. 4.4.1-152-g38d39f96

With this, no release needs a version bump commit; the git tag is the single source of truth.

[netlify]

✅ Deploy Preview for volview-dev ready!

Name	Link
🔨 Latest commit	778aee1
🔍 Latest deploy log	https://app.netlify.com/projects/volview-dev/deploys/6a8376ba1317040008e5659d
😎 Deploy Preview	https://deploy-preview-924--volview-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.