Data, Spark: Add format model TCK coverage for vectorized reads (WIP)

[joyhaldar]

Adds a TCK subclass for Spark's vectorized ColumnarBatch read path.

Four base class changes were needed:

• readOnly() - vectorized models register readers only, so write tests are skipped.
• supportedFormats() - Avro has no ColumnarBatch model registered
• assertRecordsEqual() - read tests built expectations via convertToEngineRecords, which can't work for a batch type
• Read assertions moved inside try-with-resources, columnar batches don't survive the reader closing

[pvary]

I don't really like this one.

Could we just re-define FILE_FORMATS, and FORMAT_AND_GENERATOR in TestSparkVectorizedFormatModel?

  private static final FileFormat[] FILE_FORMATS = {FileFormat.ORC, FileFormat.PARQUET};
  private static final List<Arguments> FORMAT_AND_GENERATOR

This relies on the fact, how junit works internally, but no change is required in all of the tests.

I'm open for other ideas as well, this is just the first one occured to me

[pvary]

Shall we split the base test class to read-tests, and read+write-tests?
Using this method in all test seem awkward a bit.

If we decide so, we might want to do it in a different PR