It's important for downstream apps to be able to verify that s3guard works by making the AWS client inconsistent (so demonstrate problems), then turn s3guard on to verify that they go away.
This can be done by exposing the InconsistentAmazonS3Client
- move the factory to the production source
- make delay configurable for when you want a really long delay
- have factory code log @ warn when a non-default factory is used.
- mention in s3a testing.md
I think we could look at the name of the option, fs.s3a.s3.client.factory.impl too. I'd like something which has "internal" in it, and without the duplication of s3a.s3