StatsWidget: (Idea) allow developer to show stats widgets from console

[ibgreen]

For discussion:

In probe we already store log settings in local storage.

We could also have StatsWidgets hidden by default and offer a console command to enable them.

> probe.stats = true // or
> probe.showStats()

This way, devs could easily turn on stats after a new release or when they think they see regressions.

[tsherif]

I think this could be really cool. If we had a standard way that stats indicated how they should be displayed (e.g. the typeHint property I suggested) and a standard way to register stats globally, then it would be easy to turn on a display like this.

[ibgreen]

As an alternative to fully automated Stats object detection, we could also require apps to still add StatsWidgets to their UI for this to work. Those StatsWidgets would however not show up automatically.

They could then be displayed by activating them in the console as described above.

Presumably we would also provide a programmatic interface ({display: true}) for apps that actually always want them displayed.