fix: sync kubernetes-manifest images with release versions

[mdarshadkhan1998]

Background

Previously, the individual YAML manifests in the kubernetes-manifests/ directory used generic image names (e.g., image: paymentservice) without a registry path or version tag. While the consolidated release/kubernetes-manifests.yaml file was correct, anyone attempting to deploy or redeploy a single service using the individual files would encounter ImagePullBackOff errors because Kubernetes could not resolve the image.

Fixes

#3360

Change Summary

• Updated all service manifests in the kubernetes-manifests/ directory to use fully qualified image paths.
• Synchronized image tags with the versions specified in release/kubernetes-manifests.yaml (v0.10.5).
• Ensures individual services can be independently deployed using kubectl apply -f .yaml.

Additional Notes

This change ensures consistency across the repository's deployment options. It specifically solves the issue where developers or users trying to test a specific microservice in isolation were unable to do so using the provided individual manifest files.

Testing Procedure

1. Navigate to the kubernetes-manifests/ directory.
2. Attempt to deploy a single service (e.g., paymentservice) using its individual manifest: kubectl apply -f paymentservice.yaml
3. Verify the deployment status: kubectl get pods -l app=paymentservice
4. Result: The pod should transition to Running state and successfully pull the image us-central1-docker.pkg.dev/google-samples/microservices-demo/paymentservice:v0.10.5

Related PRs or Issues

#3360

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[mdarshadkhan1998]

This PR fixes an issue where individual service manifests in kubernetes-manifests/ were out of sync with the release manifest. I have updated all image references to use the full Artifact Registry paths and version tags (v0.10.5), ensuring that individual services can be deployed or redeployed independently.

Fixes # (#3361 )