add latency predictor build readme and update test

[kaushikmitr]

This pull request adds a comprehensive build and deployment guide for the Latency Predictor v1 component. The new README.md provides step-by-step instructions for building, deploying, and testing the dual server architecture using Google Cloud Platform and Kubernetes. The documentation covers prerequisites, configuration, usage, troubleshooting, and workflow for both local development and cloud deployment.

Documentation and workflow improvements:

• Added a detailed README.md with instructions for building, pushing, deploying, and testing the training and prediction server containers using the build-deploy.sh script.
• Explained prerequisite tools and files required, including Docker, Google Cloud SDK, and Kubernetes configuration.
• Provided step-by-step setup instructions for GCP authentication, kubectl configuration, and script customization.

Deployment and testing guidance:

• Documented the deployment phase, including applying Kubernetes manifests and exposing services via LoadBalancer, with commands for checking status and troubleshooting.
• Included sample API requests and endpoints for health checks and predictions, plus instructions for viewing logs and service status.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kaushikmitr
Once this PR has been reviewed and has the lgtm label, please assign ahg-g for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @kaushikmitr. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kaushikmitr]

@kfswain @ahg-g PTAL