HADOOP-19161. S3A: option "fs.s3a.performance.flags" to take list of performance flags

[steveloughran]

HADOOP-19161

Initial design

• no tests or docs
• served up via StoreContext. Not sure about the merits of that I think it is needed so it gets down to all AbstractStoreOperation instances, but should that be where the decision is made?
• create performance is wired up.
• as is path capabilities

For testing we need to make sure ths is unset from all cost tests.

relates to #6543; the logic to set up that operation is here...that PR would just be the implementation.

Same for a delete optimisation where we'd skip parent dir probe. rename could do the same for its source dir too.

For code changes:

• [X] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
• [x] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
• [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
• [ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?