Add support for parsing loop times in Go benchmarks

[gaby]

This is a continuation of the fixes introduced in #224

    {
      name: 'Benchmark_AcquireCtx',
      value: 466.4,
      unit: 'ns/op\t    1568 B/op\t       5 allocs/op',
      extra: '2582733 times\n4 procs'
    },
    {
      name: 'Benchmark_AcquireCtx - ns/op',
      value: 466.4,
      unit: 'ns/op',
      extra: '2582733 times\n4 procs'
    },
    {
      name: 'Benchmark_AcquireCtx - B/op',
      value: 1568,
      unit: 'B/op',
      extra: '2582733 times\n4 procs'
    },
    {
      name: 'Benchmark_AcquireCtx - allocs/op',
      value: 5,
      unit: 'allocs/op',
      extra: '2582733 times\n4 procs'
    }

The 2582733 times never gets parsed using the latest version of this action. This value is how many times the loop was executed during the benchmark of the function. This is crucial data during a benchmark as it would let us know if the number of iterations run by the function has changed between code changes.

[gaby]

@ktrz Thoughts on this?

[ktrz]

Hi @gaby

I am not sure what would be the value of treating the loop execution count as another benchmark. I'm afraid that adding this as another benchmark would more likely introduce more noise than benefit. As far as understand it (from reading the doc) it is more of the metadata about the benchmark itself rather than a value to keep track of. Basically the benchmark tool will run it as many times as it needs to get a statistically significant result

[gaby]

@ktrz Fair, will close it. Thanks for your help! 💪