Update triage party configuration

[mhucka]

This updates our Triage Party configuration in various ways. On the web page itself:

• Update the title of the Triage Party page
• Change the overall look and feel, particularly the color scheme
• Remove some sections we rarely use and do other navigation cleanup
• Remove the "reactions" column from the table
• Remove some of the Triage Party tags used where they are redundant
• Change the titles of all Triage Party tags to be more understandable
• Make other changes here and there

Internally, in the configuration files of dev_tools/triage-party/:

• Refactor config files to follow current practices, for example to use Kustomize, a config.yaml file, and more
• Put custom CSS code in a custom.css file
• Add a favicon icon (using the Cirq logo)
• Expand the README.md file to match the current scheme and add much more info to help future maintainers

[mhucka]

Screenshots for documentation:

• Front/landing page

• Issue triage page:

• Issue discoverability page:

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.60%. Comparing base (4738170) to head (608d3e7).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #8080   +/-   ##
=======================================
  Coverage   99.60%   99.60%           
=======================================
  Files        1118     1118           
  Lines      100957   100957           
=======================================
  Hits       100557   100557           
  Misses        400      400           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pavoljuhas]

LGTM after addressing comments. Would it be possible to have a staging deployment so the new config could be tested side-by-side with the current one? (only if easy to do)

Thanks for improving this!

[mhucka]

Would it be possible to have a staging deployment so the new config could be tested side-by-side with the current one? (only if easy to do)

Staging on GCP is probably possible for someone who is more familiar with Kubernetes & GCP, but unfortunately I'm not familiar enough with it that it would be easy to do for me :-(.

However, it should be possible to run Triage Party in a Docker container (T.P. has a 3 line example of doing that on their front README.md file). It requires changing the configuration a little bit, though; for some reason the Cirq config files are not organized the same way as in their example. I'll give it a short try.

[mhucka]

Update:

• fixed the favicon issue
• overhauled the configuration further
• figured out how to run a local copy of Triage Party and added a script run-local.sh to do it
• expanded the README.md file to explain it all