Add TestGrid UI MVP code to this repo

[michelle192837]

Let's set this up as the canonical place for TestGrid UI development!

This should be pretty straightforward, hopefully. I think it needs:

• Import the web/ directory contents from https://github.com/GoogleCloudPlatform/testgrid.
• Update dependencies (if any) to reference https://github.com/GoogleCloudPlatform/testgrid rather than assuming it's in the same repo. (If anything, this is probably references in the UI to our protos and the API).
• Ensure we have documentation for running and testing the frontend.
• Update the documentation in https://github.com/GoogleCloudPlatform/testgrid to point here for any frontend work.
• Add a TODO issue with all the work items that are planned (or would be good) for the UI, to make it equivalent to or better than the existing UI (Get the TestGrid UI deployed with equivalent functionality #4)

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[michelle192837]

/remove-lifecycle stale

Import's done, I'll try and get some progress on this later in the month.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[michelle192837]

/remove-lifecycle stale

Going to try and finish this up in the next couple weeks.