G002: do not take autovacuum into account

See merge request !447

Keep the ascending order of redundant indexes in the H004 report

See merge request !459

* keep the ascending order otherwise, tests are unreliable because the randomness of the result set
* enable tests for redundant_indexes

fix: change imports and refactor the project structure to be able compiling pghrep (#505)

Closes #505

See merge request !458

* init Go modules, update required Go version to 1.17
* refactor imports, remove local paths of packages
* refactor the project structure: create a single point of running, get rid of the `src` directory
* adjust Makefile and Dockerfile according to the structure: remove unnecessary commands

English grammar fix

See merge request !455

fix: l003 sort

See merge request !451

Fix wording total->average number of files per day

See merge request !453

Update copyright for 2021

See merge request !452

Change to AGPLv3

See merge request !449

L003: do not analyze multi-columns PKs, fix JSON syntax

See merge request !448

- Skip multi-column PKs: analyzing each column in them may cause a huge slowdown,
- fix JSON syntax (previously, jq was not complaining, but syntax lacked some commas)

fix: dockerfile, pghrep build

See merge request !446

feat: improved docker images storage

See merge request !445

fix: typo in error message

See merge request !444

Link fix + better GIF quality

See merge request !442

No year in copyright; README: -h vs --pg-../--ssh-..

See merge request !441

README: Ask for a gitlab star

See merge request !440

Support of PG 12 was realized not fully. It is fixed.

F004 report, which used pg_class.relhasoids column does not process correctly on Postgres 12. So this report was reworked to remove using of pg_class.relhasoids.

In the case when `sudo` requires a password on the checked server(s), data collection for the A008 and D002 reports fails.
Now it is possible to specify such a password using the environment variable `SSHSUDOPASSWORD`.

Sometimes during query analisis we neet to know query id, but it does not display in K003 report. So query id added to first column of K003 report's table.

fix: run_checkup.sh

See merge request !436