* 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

* Reverted hardcoded block number and changed to use CI var HIVEMIND_MAX_BLOCK.
* Please add a possibility to set HIVEMIND_MAX_BLOCK.
* operation_extractor:
** name of parameter `hivemind_address` changed to `hived_url` as we
   scan blocks from `hived`
** added description to the script

* New script for running benchmarks
* Benchmarks are now runned several times to cheat caching
* Data from each run is combined together

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

See merge request !231

* 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

Removed accidentally pasted text.

Enabled running a script.

Add extension pg_stat_statements to postgres on CI

Create database template template_hive_ci

Created python functions for pgwatch2 in template

Create docs for monitoring postgres

Setup monitoring by unprivileged db user

Minor changes

Improved docs for db monitoring

Increase allowed number of connections for pgwatch2

Eliminated NULL from hive_posts::root_id column. Since actual ID is not available yet during inserting root post, this column is updated at the end of initial-sync or processed block.
Simplified hive_posts_root_id index, to speedup list_comments_by_root queries
Optimized query used to access posts inside list_comments_by_root.
Deleted obsolete file scripts/update_hivemind_db.sql