Publish source and contribution paths for NGC-delivered API services

Is your feature request related to a problem? Please describe.

Some services required by the self-managed NVCF stack are deployable through NGC artifacts, but users and contributors cannot yet fully inspect, build, test, or contribute to every service from the public repository.

This affects OSS readiness for:

• NVCT API
• NVCF API
• ICMS API
• ESS API
• NVCF Go Worker (Utils, Init, Tasks, LLM Credential Helper)
• NVIDIA API Keys (NAK)

Describe the solution you'd like

Provide a public source and contribution path for each NGC-delivered API service used by the self-managed stack. This is an umbrella issue for tracking the service set together until each service has its own implementation plan.

For each component, document:

• Public source location or current release status.
• Build and test commands.
• Container and Helm chart provenance.
• Ownership (CODEOWNERS) and contribution path.

Describe alternatives you've considered

N/A

Additional context

Suggested acceptance criteria:

• Each service listed above has a documented OSS status.
• Components that are already public can be built and tested from documented commands.
• Components that are not yet public have clear status and next steps.
• The artifact manifest links to the source or status entry for each service.

By submitting this issue, you agree to follow our code of conduct and our contributing guidelines.

Start with the artifact manifest and the listed services, then read CONTRIBUTING.md and inspect each component's current source or release status. Document the source or status, build and test commands, container and Helm provenance, CODEOWNERS, and contribution path; done means every service has an OSS status and a linked source or next step.