Add semantic version tags (v0.x.y) for Go module release tracking

[sumanarukonda]

Hi Team,

We’re using sigs.k8s.io/json as a dependency in our Kubernetes-based projects, and we’ve noticed that the module currently uses commit-based pseudo-versions (e.g., v0.0.0-20241010143419-9aa6b5e7a4b3).

It would be very helpful if semantic version tags (e.g., v0.1.0, v0.2.0, etc.) could be introduced. This enables:

• Better dependency tracking and reproducibility.
• Compatibility with compliance tools (like Black Duck).
• Easier identification of changes between versions.

For reference, the module is already published under Apache 2.0, so formal tagging would mainly improve dependency management and security scanning.

Thank you.