Add the ability to intercept File IO by specifying a wrapper class

[andrew4699]

Description

This PR adds the ability to provide wrappers around File IO by specifying a wrapper factory. It comes with a no-op wrapper factory which performs no wrapping. I did not implement any specific type of wrapper as there can be a separate discussion on which interceptors would be useful to put in the repo if any, but it should be uncontroversial that the ability to intercept this is generally useful for use cases such as metrics.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• I added a unit test testFileIOWrapper.
• All existing tests work with the NoOp wrapper.
• I ran through the quickstart and verified that I could perform all the same table operations.

Checklist:

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• If adding new functionality, I have discussed my implementation with the community using the linked GitHub issue
• I have signed and submitted the ICLA and if needed, the CCLA. See Contributing for details.

[andrew4699]

@collado-mike I changed it to just be FileIOFactory and added MetricRegistryAware to be consistent with the other xAware interfaces.

[collado-mike]

Nice. Minor suggestion for an additional metric and add a javadoc and we'll be good

[collado-mike]

measure files deleted? Seems like a useful metric (especially if it spikes real high real fast 😅)

[andrew4699]

Added some testing for measuring deleted files. Originally I left it out as MeasuredFileIOFactory is just a test class but I may as well add it as an example.

[collado-mike]

oh! didn't realize this was a test class. It seems super useful to me. Maybe move it into src/main?

[andrew4699]

This implementation isn't that great since it doesn't clean up IOs and its metrics may not be super useful, it was just intended to be super simple to confirm that File IO is wrapped properly.

[snazy]

I think, this is redundant

[andrew4699]

factoryType could be a top level config, but I made it io => factoryType to push a grouping of io-related configs. For example if you choose to make a metrics-emitting implementation of FileIOFactory, you may want some further configs.