Cloud Tasks should read registry credential secrets from ESS instead of the inline account response

Problem

NVCF API stores registry credential secrets in the External Secret Store (ESS), but it also fetches them back and includes the secret values inline in the internal account details response consumed by Cloud Tasks. Cloud Tasks then reads the inline secret to build image pull secrets.

Sending secrets inline in a service to service response is unnecessary now that the value already lives in ESS. Telemetry secrets already follow the pattern where NVCF populates ESS and the downstream reads directly from ESS.

Desired behavior

• NVCF API omits the secret value from the account details response and instead includes the registry credential id.
• Cloud Tasks reads the registry credential secret directly from ESS by id, mirroring the telemetry pattern.
• Rollout is order independent: if an older NVCF still returns the inline secret and no id, Cloud Tasks uses the inline value.

No database schema change is required.

Locate the Cloud Tasks consumer of the internal account details response and compare its credential handling with the telemetry ESS pattern. Trace the NVCF response fields and the ESS lookup by registry credential id. Done means new NVCF and Cloud Tasks versions use ESS without inline secrets, while older inline-secret responses still work and no schema change is introduced.