Usability enhancements for HTML

[jeffwright13]

1. If there are warnings or errors, change color of Output Sections tab to yellow/red
2. Expand/Collapse All Tests button on Results pages (https://stackoverflow.com/questions/50393204/expand-all-collapse-all-button-js)
3. Each Results tab should have sortability by fqtn, time and outcome
4. Triple-click result button to select all label text
5. Highlight/outline header tab that's currently active
6. ~~Link-like content in test cases should be hyperlinked and clickable~~ NOT FEASIBLE
7. 'About' page should link to Failures, Passes, etc. via lastline
8. ~~Migrate buttons at top to navbar~~ (not needed anymore)
9. ~~Highlight on hover for test case buttons~~ DONE
10. ~~Zebra highlighting for results~~ will not do
11. ~~Tab bar colors~~ DONE
12. ~~Top-level buttons (About | Passed | Full Output | etc.) should be sticky at top of page~~ DONE
13. ~~Horizontal scroll bar should be visible at bottom of browser if page content extends beyond the page~~ DONE
14. ~~Visual delineation between Results and Sections tabs~~ DONE

[jeffwright13]

As for (4) above, this is the #1 use case item that would improve usability, at least for me. So, something like this should be able to open up the file Operation.py locally if clicked:

>       assert Timeout.timeout(
            lambda: .check(
                self.device,
                "actualValue",
                real_value,
            ),
            timeout=timeout,
            interval=1,
        ), "Failed sanity check"

E       AssertionError: Failed sanity check

../gems/operations/Operation.py:76: AssertionError

---

Possible template for implementing custom file:/// solution: https://blog.mattheworiordan.com/post/13174566389/url-regular-expression-for-links-with-or-without

---

2022-11-27 Update: Because of security reasons, opening files on the local filesystem is not allowed from web browsers. One way I can think of doing this is by actually embedding the source code in a foldable section in the HTML itself...but then, Pytest already kind of does this with its traceback handling, so this is just gilding the lily.