Expose k6 HTML reports

A/C

• Add a k6 HTML report for each scenario/approach combination, colocated with the test-specific result images we already produce.
• This HTML report is produced automatically by k6 if configured correctly (see below)
• Extend the $scenario.md file with links to these HTML reports, each placed immediately after the appropriate approach header and before its single result image. The name of the link shall be "k6 Report".

Config

In order to produce a K6 HTML report, the following env vars need to be set for the k6 process. The name of result.html has to be dynamically templated - this is just an example:

K6_WEB_DASHBOARD=true K6_WEB_DASHBOARD_EXPORT=result.html 

Test

Fail the performance test with a clear message if the k6 HTML report is not created.

Example

Let's consider the folder web-client-reactor-netty-5k-vus-smooth-spike-get-post-movies-call-depth-5.

It currently contains these files:

• loom-netty.png
• loom-tomcat.png
• webflux-netty.png

In future, it will contain these additional files:

• loom-netty.html
• loom-tomcat.html
• webflux-netty.html