Goal

There is a tool that converts single leapp repots into an HTML page with tables and statuses of each node: https://github.com/oamg/leapp-report-analyzer

Currently, the role does what leapp does, but the result is not nicely visible for users. You have leapp reports inside each node but no high-level overview.

At the end of upgrade, the upgrade role can fetch all leapp repots to the control node, and run the report tool to build an HTML report. 

We will need to contact the UX team to identify how we can improve the HTML report (font, style, etc.).

At the very least - the role can give some basics instructions to users at the end of the (pre-)upgrade about what happened and where to find log files to see more details. @Marc Muehlfeld suggested a great idea to copy leapp analysis reports from managed nodes to a dir on the control node. Until we do the HTML report (not sure if we do this), at least this will help to view files on the controller. I'll open a ticket for this. The ansible fetch module does this - https://docs.ansible.com/projects/ansible/latest/collections/ansible/builtin/fetch_module.html

Possible improvements:

• multiple pages/tabs - one page lists inhibitors by severity - a table for each severity
• * the first column is the inhibitor name/title, which is perhaps a link to more information about that inhibitor (details, what remediations are needed)
• * the second column is the list of hosts which encountered that inhibitor - each host is a link to that host's entry on the hosts page - might need to make this a scrolling text box/menu to handle more than N hosts, where N defaults to 10? 20? and is configurable
• one page lists each host that has an inhibitor
• * first column is the hostname
• * second column is the list of inhibitors in order of severity - the inhibitor name/title is a link to more information
   

  Acceptance criteria

A list of verification conditions, successful functional tests, or expected outcomes in order to declare this story/task successfully completed.

• Upgrade role runs the report at the end of upgrade in an `always:` block to ensure reports are gathered from all nodes.
• UX team approves the resulting HTML doc