Support output from unit tests (not just Cypress E2E tests) in test section of console

**Is your feature request related to a problem? Please describe.**
Currently the amplify console supports E2E tests with Cypress and can show the report and artifacts in a nice format within the test section of each build. Unfortunately there is not a way to show unit test results (from Jest for example) in this section. Even if you run your tests in this section, a non-zero exit code won't actually break the build and it will still deploy.

**Describe the solution you'd like**
Allow the test section to accept different, common report formats so that tests can be shown in the nice UI of the test section. Most test runners can output into common formats like junit reports so if the console can support 2-3 of these that would be great. Cypress seems to use the mochawesome format so perhaps some inbuilt converters into this format?

**Additional context**
Currently we have to place linting and unit tests during the build phase. Failing tests will break the build at least but you have to dive into the output to figure out which ones.

No repository files or tests are named. Start by tracing the console test section and its existing Cypress report handling, then compare the requested Jest and common report formats. Done means supported unit-test results render in the test UI and failing tests prevent deployment.

Written by the indexing model from the issue text.