Add hashi_vault example

See merge request !2

Vault pki

See merge request !1

* You can use custom certificate encoded in x509 or generate CA with Hashicorp Vault

I still can't figure how to specify pgsql schema in template. I used {{schema}} and {{search_path}} but both seems empty in creation script.
Tested creation of creds after root creds rotated. Probably I should test new role creation after rotate

Update config, initial sql script, fix .env.example, add README and Makefile, move logging into proto, add capabilities

* Update config so Vault will use specific pgsql schema and and creds with ha_locks table as well
* Disable proxy_protocol so you can access vault directly without web proxy
* Specify seal type just for removing annoying warning at vault start
* Create new db, schema, role and hardening permissions on tables
* PGSQL data will be stored in docker volume
* Vault config will be mounted into docker not a directory. Be cause I did not found how prevent Vault init script to change rights on files inside configs directory
* Makefile and README contains goals and descriptions for guide https://learn.hashicorp.com/vault/secrets-management/sm-dynamic-secrets
* Payloads is still in WIP status and added for future

This will not convert any message of vault logs into JSON, but docker logs will looks like
```
docker logs vault-dev-single_server_1
==> Vault server configuration:

                     Cgo: disabled
              Listener 1: tcp (addr: "192.168.9.2:8200", cluster address: "192.168.9.2:8201", max_request_duration: "1m30s", max_request_size: "33554432", tls: "disabled")
               Log Level: trace
                   Mlock: supported: true, enabled: false
           Recovery Mode: false
                 Storage: file
                 Version: Vault v1.4.0

==> Vault server started! Log data will stream in below:

{"@level":"info","@message":"proxy environment","@timestamp":"2020-05-05T11:06:51.170431Z","http_proxy":"","https_proxy":"","no_proxy":""}
{"@level":"warn","@message":"no `api_addr` value specified in config or in VAULT_API_ADDR; falling back to detection if possible, but this value should be manually set","@timestamp":"2020-05-05T11:06:5...

Signed-off-by: Shutkin Yura <shutkin.yurii@gmail.com>

Signed-off-by: Shutkin Yura <shutkin.yurii@gmail.com>

Signed-off-by: Shutkin Yura <shutkin.yurii@gmail.com>

Signed-off-by: Shutkin Yura <shutkin.yurii@gmail.com>

Signed-off-by: Shutkin Yura <shutkin.yurii@gmail.com>

Signed-off-by: Shutkin Yura <shutkin.yurii@gmail.com>

Signed-off-by: Shutkin Yura <shutkin.yurii@gmail.com>

Signed-off-by: Shutkin Yura <shutkin.yurii@gmail.com>

Signed-off-by: Shutkin Yura <shutkin.yurii@gmail.com>

WIP vault unseal migrate searching for version with possibility of using shamir after transit seal type