Pull request: fix K8s Deployments to run correct service binaries

[thenovatasha]

Summary
Pods failed to start because the manifests tried to run ./, but the binaries live in /go/bin. This PR updates the command to call the binary by name, relying on the image PATH (which includes /go/bin).

What changed

For each service (frontend, geo, profile, rate, recommendation, reservation, search, user), set:

command: [""]
instead of ./ or an absolute path.

Why this is needed

Events showed:

RunContainerError: exec: "./": stat ./: no such file or directory

The image installs built binaries under /go/bin/.

Calling the binary by name works because /go/bin is on PATH.

How it was tested

Applied the updated Deployments on a clean minikube cluster.

Verified rollout:

kubectl rollout status deploy/
kubectl get pods

Reached the frontend via port-forward and ran a simple request:

kubectl port-forward svc/frontend 5000:5000 &
curl -f http://localhost:5000/ || true

Sanity check from a pod:

kubectl run curl --rm -it --image=curlimages/curl -- \
  curl -sS http://frontend.<ns>.svc.cluster.local:5000/health

Checklist

• Pods reach Running for all updated services.
• kubectl apply --dry-run=server passes.
• Basic request path returns a 200.