feat: generate the Dashboard - base structure

[laurentsenta]

example output:
https://singulargarden.github.io/gateway-conformance/

example workflow:
https://github.com/singulargarden/gateway-conformance/actions/workflows/deploy-pages.yml

Adds data generation

• munge.js: takes a go test output and generates a nicer data structure
• munge_sql.js: load all the outputs into a single sqlite db
• munge_aggregates.js: generate resources for the website generation (content pages and data files)

Generate the dashboard

• in www/
• using Hugo

Follow-ups (see #123)

• complete drill down (fix slugs, pathing, and breadcrumbs)
• complete logs rendering (nesting for logs)
• more prominent jobs urls

[galargh]

FYI, I didn't review SQL too closely - assuming it's OK if it works. And HTML, I'd say that the visual review we did together during demo last time is good enough. All in all, good to go from my side :)

[BigLep]

Very nice!

A few things coming to mind:

1. Do we have docs describing the flow of the dashboard generation? For example, I can't remember, are we pulling the conformance results from the CIs of other projects (like Kubo, Boxo) or are we running the conformance tests ourselves in this repo? (it looks like we pull the results per https://github.com/singulargarden/gateway-conformance/actions/runs/6075886236 ). It would be good to have docs on "how to add your implementation to the dashboard". I think that will cause the right high level info to surface.
2. Assuming we're pulling results from other repos, what's the way for someone to see:
   • what commit of the conformance test suite we ran
   • what commit of the implementation we ran against
   • date when these results are from
     Is that all in the job log?

Good stuff.

I would also talk with @lidel on how we give visibility to this dashboard from https://specs.ipfs.tech/

[laurentsenta]

@BigLep thanks for the nice and detailed feedback, I'll update #123 to take into account your notes.