Changed methodology for benchmarks

• 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

tests/tests_api

-Subproject commit 820b1f1d87dea8305324ed3718babe7006c269ec
+Subproject commit 1ae2a4b1367139e7954b31596eaa4bf65e6aa68e