chore: publish performance data to gh-pages

[sadym-chromium]

• Use benchmark-action/github-action-benchmark@v1 to automate perf metric storage and deployment.
• Switch repo's GitHub Pages to deployment from branch gh-pages. Required, as now there are 2 sources of information for gh-pages (WPT + performance).
• Update WPT report to override wpt/index.html and wpt/wptreport-2023.html in gh-pages branch.
• Add index.html with links to the perf metrics and to the WPT reports the root of gh-pages branch.
• Example perf page: https://googlechromelabs.github.io/chromium-bidi/bench/index.html

TODO

• After the PR is merged protect gh-pages page.
• Before merge clean up bench/data.js.
• Before merge switch back to publishing WPT report and perf metrics only on main PRs.

[browser-automation-bot]

Benchmark

Benchmark suite	Current: 5ecdcea	Previous: dc085ec	Ratio
ubuntu-latest-new-headless-node:test_performance_screenshot	152.0256519317627 ms	169.04306411743164 ms	0.90
macos-latest-new-headless-cd:test_performance_screenshot	2888.0240440368652 ms	1749.3316173553467 ms	1.65
macos-latest-headful-node:test_performance_screenshot	2984.7654342651367 ms	2945.427417755127 ms	1.01
macos-latest-headful-cd:test_performance_screenshot	3746.2746143341064 ms	1536.3247871398926 ms	2.44
ubuntu-latest-old-headless-node:test_performance_screenshot	282.05833435058594 ms	281.720495223999 ms	1.00
macos-latest-old-headless-cd:test_performance_screenshot	241.12024307250977 ms	291.26501083374023 ms	0.83
macos-latest-new-headless-node:test_performance_screenshot	2181.254196166992 ms	2148.181390762329 ms	1.02
macos-latest-old-headless-node:test_performance_screenshot	346.4141845703125 ms	353.8914203643799 ms	0.98
ubuntu-latest-new-headless-cd:test_performance_screenshot	185.6924057006836 ms	164.56851959228516 ms	1.13
ubuntu-latest-old-headless-cd:test_performance_screenshot	279.1600227355957 ms	265.1052951812744 ms	1.05
ubuntu-latest-headful-node:test_performance_screenshot	167.65499114990234 ms

This comment was automatically generated by workflow using github-action-benchmark.

[sadym-chromium]

@Lightning00Blade @OrKoN WDYT about this approach?