dotnet: move the Wasm compilation into the first run (cherry-pick)

Backmerge of #274 (ad5e397):

- Format in-depth.html
- Add empty in-depth.html sections for the new workloads
- Add unit tests to check that all benchmarks have a matching in-depth entry

First steps to address #199.

Add Wasm descriptions to in-depth.html, grey out non-default workloads

Add Wasm descriptions to in-depth.html, grey out non-default workloads (backmerge of #275)

Use the benchmark definitions from JetStreamDriver.js to add tags to each workload title.

- Add tags
- Add links to run workload matching a tag
- Add links to run a single workload
- Improve in-depth.html css a bit to use less spacing around headers and the first definition
- Use relative link from index.html => in-depth.html 

Backmerge of #288

We don't want CSS animations to interfere with short running measurements which
can easaily happen if you only run a single workload.

Adds missing in-depth.html entries.

- Update version number to the full format "3.0" in more places
- Remove link for hosted main-branch in README.md

- Add basic tests/run-license.mjs license header checks
- Add more license headers to new benchmark files

Note: This keeps some older benchmark files untouched that have separate licenses desciptions.

Fixes #150
Backmerging PR #278

While deploying JetStream3 on browserbench.org a bunch of the assets
couldn't be loaded due to firewall restrictions. This change upstreams
the hotfixes back to the main repo.

Workaround firewall blocking on browserbench.org