99designs/keyring v1.1.4; fix linux / secret-service bug

[pda]

Fixes #513

1c0b58a from #481 released in v5.1.0, as part of a substantial overhaul, introduced a keyring.Has(key) check where previously it just hoped for the best and the aws-sdk ended up attempting to Keyring.Get(key) as part of the credential provider. In the secret-service backend (linux / libsecret / gnome keyring), Get was unlocking the item as needed, but Has was not unlocking the items/collection; instead it would return empty strings for a locked collection.

99designs/keyring#61 fixes the upstream Keyring.Has() bug, and this patch brings the resulting v1.1.4 release into aws-vault.

This go.mod & go.sum update is the result of:

go get -u github.com/99designs/[email protected]

Manual testing:

# lock all keyring collections
gnome-keyring-daemon -r -d
# ** Message: 15:49:25.164: Replacing daemon, using directory: /run/user/1000/keyring
# GNOME_KEYRING_CONTROL=/run/user/1000/keyring
# SSH_AUTH_SOCK=/run/user/1000/keyring/ssh

# demonstrate bug in previous version
./aws-vault-5-2-0 exec testprofile -- aws sts get-caller-identity
aws-vault: error: exec: Error getting temporary credentials: profile testprofile: credentials missing

# demonstrate fix
./aws-vault exec testprofile -- aws sts get-caller-identity
# {
#     "UserId": "AID______________",
#     "Account": "___________",
#     "Arn": "arn:aws:iam::_________:user/_______"
# }