Code coverage as a bundle metric

Two things:
- while bundle size in most “visible” metric the main metric is the amount of code executed, not downloaded
- ‘size-limit’ is not just “size control” utility, but “size discovery” as well

wondering, would this extra metric be useful, including usecase for creation solutions with less “boot time footprint”. The “code usage percentage” falls into the same bucket as “code size” and “execution time”, so it would not be that alien for size-limit functionality, however there is an open question how to make it actually usable and useful.

> based on https://twitter.com/patak_js/status/1451440832347877377?s=21