HTML test report doesn't provide sufficiently good user experience

[bartekpacia]

I don't like the experience that our HTML report (generated with maestro test --format HTML flow.yaml) provides.

• Better appearance

  • as in: more consistent with Maestro CLI output, Maestro Studio, and the AI report HTML

• Use Tailwind instead of Bootstrap

  • to minimize number of dependencies and cognitive load. We already use Tailwind in Maestro Studio and AI report HTML.

• List of commands executed in each flow

  • this was initially implemented in #1750 but had been removed before the PR was merged

• Separate HTML report for each flow, with easy toggling between them

  • just like it works right now in AI report

• Merged with AI report, to keep the experience consistent and easy to navigate

• Include Insights in the report:

  Insights are those INFO and WARNING under commands

  

fyi @proksh