Vault Config Sourcer Fixes

[paladin-devops]

Fixes #2333.

This PR fixes a bug where an application deployed with the Vault config sourcer plugin using a dynamic secrets engine in Vault was inaccessible. waypoint exec would hang forever, the address provided by the URL service would be inaccessible, as well as any other way to access the application outside of the URL service.

A subsequent bug which is also fixed in this PR is that dynamic secrets were previously being overwritten as an empty map when the secret was renewed. This is the normal behavior of the Vault lease API, as that API does not return the data of a secret whose lease is renewed. However, now, if a lease is successfully renewed, the Vault config sourcer plugin will still retain the data from when the secret was originally read.

Little bonus in this PR - the CEB binary will now include the git commit in its version, whereas previously only the last major version was logged as the version - this is the Makefile change.

[paladin-devops]

Quick, weird update on the behavior here! Immediately after the deployment, the secret is indeed set in my environment. Only after ~10 seconds or so do I run into that warning log, and the value is unset.

Run right after the deployment:

% waypoint exec env
Connected to deployment v25
USERNAME=vault-generated-username
PASSWORD=vault-generated-password

Nothing returned for attempts after ~ 10 seconds post-deployment:

% waypoint exec env | grep USERNAME
% waypoint exec env | grep PASSWORD

UPDATE: this has been fixed now, updated PR description.

[briancain]

I think you still have some outstanding TODOs, but I got some review here anyways! ✨

[briancain]

🖖🏻