Expose build version and commit metadata for NVCF control plane services

Description

NVCF control plane services do not expose a consistent way to query the exact build version and source commit of a running service. This makes it difficult to identify what is deployed during incident investigation and environment validation.

Notes:

• Define stable endpoint path and payload contract that all in-scope services share
• Define a reusable shared-library or standard implementation pattern for Go services
• Version and commit metadata must be injected from the build pipeline into each service artifact; runtime Git access is not acceptable
• Roll out the agreed implementation with each service owner

Definition of Done

• The schema contains an unambiguous service release/build version using semver and source commit SHA
• The endpoint does not confuse service build metadata with API route versions
• The access model supports cluster operators and QA teams without exposing sensitive build or environment data
• Go services use a reusable library or documented common implementation pattern
• Build pipelines provide immutable version and commit values to service artifacts without relying on runtime Git repository access
• Each in-scope service exposes accurate metadata for the running artifact
• Automated tests verify the endpoint contract and injected metadata
• Documentation explains the endpoint, fields, access requirements, and an example query