[FLINK-8148][yarn/s3] fix test instability in YarnFileStageTestS3ITCase

[NicoK]

What is the purpose of the change

YarnFileStageTestS3ITCase.testRecursiveUploadForYarn verifies that the test directory used is cleaned up by YarnFileStageTest.testCopyFromLocalRecursive which should clean up the directory (in a finally block). However, for S3, we may not always see our own deletes.

Quoting from https://aws.amazon.com/s3/faqs/ here:

Q: What data consistency model does Amazon S3 employ?
Amazon S3 buckets in all Regions provide read-after-write consistency for PUTS of new objects and eventual consistency for overwrite PUTS and DELETES.

Brief change log

• Remove a check for a deleted directory since we may not see our own delete yet
  with S3.

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? not applicable

[StephanEwen]

Makes sense, +1

[zentol]

merging.

[zentol]

will fix the checkstyle violation on the way.

[NicoK]

oh, sorry for that