text: Title: CI: Performance Benchmarking during CI
  Body: We want our CI to assess the performance of the code to avoid regressions. 
  These are benchmarks that should run via Github Actions, but also be optionally disabled/enabled via a simple boolean flag.
  
  * Runtime Benchmarks:  Some of these benchmarks should time the execution of certain cleanlab function calls, and report error if the execution time in this version of the code has significantly increased from the previous version of the code. Ideas for these cleanlab function calls including copying some from the more substantial unit tests, or taking some from: github.com/cleanlab/examples/
  
  * Performance/Accuracy Benchmarks:  Other benchmarks should measure the accuracy of cleanlab's label error detection capabilities and CleanLearning's supervised learning accuracy.  These would report error if the accuracy of certain function calls in this newly updated version of the code has significantly decreased from the previous version of the code.  Ideas for sources of data/performance numbers for these benchmarks include: 
  * Copying some of the more substantial unit tests
  * [Examples](https://github.com/cleanlab/examples/) notebooks, e.g. in particular: 
      1. https://github.com/cleanlab/examples/blob/master/classifier_comparison.ipynb
  * Tutorial Colab notebooks
  * Benchmark repos such as:
      1. https://github.com/cleanlab/label-error-detection-benchmarks
      2. https://github.com/cleanlab/ood-detection-benchmarks
  
  
  