Integrate AOT code size tooling with IDEs

It would be nice if users could trigger AOT code size tooling analysis directly from the IDE.

Goals:
Make users aware of when they might have a code size problem directly from their IDE just like the performance page gives them an idea they might have a memory or cpu performance issue without leaving the IDE.

A couple plausible workflows:
1. Every time a profile or release build is generated, display the total code size in the console with a link to view a detailed code size breakdown in DevTools.
2. Display the code size for the app integrated within the performance summary page. The summary page could provide a link to documentation on using the command line code size debugging tools if the code sie is a concern.

Fyi @kenzieschmoll