Improve build logging and bundle analysis

[maier49]

Currently our build logging output is insufficient to provide users with any real insight into their bundle sizes or application performance. Similarly, the build logging is decoupled from our bundle analysis, which itself has inconsistent behavior and doesn't make it easy to discover the causes of bundle size.

Overall we want to improve our build logging and build out a "dashboard" style summary of the build

Possible CLI Logging Improvements

• Listing sizes by Chunk instead of showing assets
• Showing large dependencies for large chunks, or otherwise providing details on chunk size
• Excluding bootstrap/runtime chunks from output
• Provide additional information that may inform the user as to the potential performance of their application such as a lighthouse score for applications that use BTR.
• Insights into what happened during btr (e.g. listing discovered pages, slow pages etc.)
• Link to an improved report/dashboard
• Show where and why we split code
• Show information on .dojorc flags and command line flags

Build report/dashboard

The linked report should be an improved version of what our current bundle analysis tool provides that (potentially):

• Shows app dependencies
• Provides basic build information like that presented from the CLI
• Links to a visualization of the build's output like that created by the existing BundleAnalyzerPlugin
• Shows an interactive, informative view of the App's .dojorc configuration

[samends]

Think some of these suggestions can be taken into account as well: #42