* Usage of pytest-benchmarks is dropped since it call tests
  sequentially which very long time to complete, instead original
  tavern tests are used
* Time measuring is done via durations switch to pytest and tavern
* During benchmarking validate_response.py is disabled using nevly
  introduced env variable
* Each run creates xml junit file with time data
* After all runs data from files are combined and report file is
  generated
* Tests above threshold are marked with red

Do not allow benchmark tests to fail, failed test is a failed job. Changed html file names to avoid confusion

* added script to process xml reports
* script will parse xml reports and create html reports with api
  execution times
* if execution time is greater than treshold it will be marked on red
  and task will fail