Log gas for one property test run

Currently using property tests means you forfeit your ability to see logs or gas usage in the `dapp test` output, would like a way to still see debug information like that so using property tests is truly a no tradeoff feature.

This is a tough problem as a run may not fail but still may not represent the expected usage of the contract (ie: test function returns early because a number given as a parameter was too large). Could be solved with some sort of heuristics to detect a test run with a median gas usage (or some other metric)?

Could also be solved by giving the test developer a way to specify if a run functioned perfectly as expected (no early returns, etc).

wdyt?

Start at the dapp test property-test output path and determine how logs and gas usage are currently omitted. Compare the proposed representative-run heuristic with letting test developers mark valid runs; done means a property test can expose debug information and gas usage without hiding early-return behavior.

Written by the indexing model from the issue text.