Microbenchmark build step

[bialesdaniel]

Problem Statement:
Currently, developers are having trouble merging PRs due to microbenchmark failures in the Jenkins builds. The microbenchmark results are not stable so developers will just rerun the build until they get the microbenchmarks to pass. As a result, the microbenchmarks are not frequently used on a per build basis.

Temporary Solution
The running the microbenchmarks have been temporarily disabled in jenkinsfile-nightly.

Long-Term Solution

• Running microbenchmarks will be removed from the normal build pipeline. The normal build pipeline will still check for compilation issues with the microbenchmarks
• Re-enable microbenchmarks in the nightly build
• Change the run_microbench.py so that a violation of failure thresholds does not fail the build. In fact, the failure thresholds become somewhat meaningless
• Store the results of the microbenchmarks in TimescaleDB
• Create Grafana visualizations that show benchmark throughput results over time for each benchmark
• Create slack alerts for microbenchmark performance regression