🛤️ Tracking: Periodic Perf Benchmarking

[j-lanson]

Similar to how Rust does it, we should have a page on our website that records and displays changes to the performance of Hipcheck over time, as the repository changes.

We should have an xtask called benchmark that takes a config file of a list of targets and executes hc check against them with benchmarking turned on. Usage: cargo xtask benchmark <CONFIG_FILE> [--out <OUT_FILE>], where --out is optional. This will write a file to site/static/perf/ with the name <TIMESTAMP>.csv. The execution should record our internal benchmarking stats, as well as linux ram statistics like "max resident set size". Use this Rust benchmarking library as well.

The config file should be a .kdl file, and target some basic repos as well as some of hipchecks own dependencies.

• - Implement benchmark xtask

Once we have this, we need a CI cron job action that will invoke the benchmark xtask once a week and create a PR requesting to merge the new file in site/static/perf into main.

• - Add CI job to execute benchmark xtask

Finally, we need to add a <SITE>/perf page to display the data in these .csv files.

• - Add /perf page to site to display benchmark xtask output