S3a operations keep retrying if the password is wrong

If you do a hadoop fs command with the AWS account valid but the password wrong, it takes a while to timeout, because of retries happening underneath.

Eventually it gives up, but failing fast would be better.

1. maybe: check the password length and fail if it is not the right length (is there a standard one? Or at least a range?)
2. consider a retry policy which fails faster on signature failures/403 responses