fix(packaging): point the nuspec's projectSourceUrl at the release tag

[jpicklyk]

What

projectSourceUrl in packaging/chocolatey/logtapper.nuspec.tmpl now points at the source tree of the tagged release, not the repo root:

https://github.com/jpicklyk/LogTapper/tree/v{{VERSION}}

For 0.13.3 this renders as .../tree/v0.13.3. projectUrl stays at the repo root.

Why

Chocolatey's automated review flagged that projectSourceUrl and projectUrl were identical. It asked us to make sure projectSourceUrl points to source code, or to remove it. The note was advisory, not a required change. Linking to the release tag is the more accurate value anyway: it names the exact source each package version was built from, and it no longer duplicates projectUrl.

Reviewer notes

• The v prefix matches the repo's tag scheme; releaseNotes in the same nuspec already uses releases/tag/v{{VERSION}}. v0.13.3 exists on origin.
• node scripts/render-packaging.mjs --check renders every template cleanly, and npm run test:scripts passes 5/5.
• verify-chocolatey.yml runs on this PR because it touches the package.
• The change reaches Chocolatey only on the next push. If the flagged version is still in moderation, re-dispatch the publish workflow after merge: gh workflow run publish-packages.yml --ref main -f version=0.13.3 (versions that aren't approved yet are pushed again on a re-run).

🤖 Generated with Claude Code