VaultConfiguration#validateAndCopyVaultConfiguration exception messages do not correctly use template parameters

[sleberknight]

This is a very minor issue, but the exception messages generated in VaultConfiguration#validateAndCopyVaultConfiguration don't correctly use the Guava template parameters:

// ...

checkArgument(isExistingPath(configuration.getVaultPasswordFilePath()),
        "vault password file does not exist: {}", configuration.getVaultPasswordFilePath());

// ...

checkArgument(isExistingPath(configuration.getAnsibleVaultPath()),
        "ansible-vault executable does not exist: {}", configuration.getAnsibleVaultPath());

// ...

The Guava Preconditions#checkArgument requires %s as the template parameters.

Fortunately, Guava still includes the values in the generated String, albeit at the end, e.g.

vault password file does not exist: {} [/home/ec2-user/.vault_pass.txt]

so you can still determine the file that doesn't exist.