Parquet-Avro does not support field removal

Parquet avro does not support removal of fields, when used with the new compatibility layer:

Given a parquet file written with parquet avro at v1 and the following schema:

```Java
record FooBar {
long foo;
string bar;
}
```

And the following configuration settings:

```Java
job.getConfiguration.setBoolean(AvroReadSupport.AVRO_COMPATIBILITY, false)
AvroParquetInputFormat.setAvroReadSchema(job, avroReaderSchema)
```

A job fails when trying to read it using schema version v2:

```Java
record FooBar {
string bar;
}
```

With the error:

```Java
org.apache.parquet.io.InvalidRecordException: Parquet/Avro schema mismatch: Avro field 'foo' not found
at org.apache.parquet.avro.AvroRecordConverter.getAvroField(AvroRecordConverter.java:159)
```

It looks like because it sees the field in the original version it assumes the new version must expect it, but this case just means that the field was removed. Avro schema resolution dictates that you just ignore this field, since it is not relevant in the new version.

**Reporter**: [Thomas Omans](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=eggsby)

_{**Note**: *This issue was originally created as [PARQUET-465](https://issues.apache.org/jira/browse/PARQUET-465). Please see the [migration documentation](https://issues.apache.org/jira/browse/PARQUET-2502) for further details.*}

Start at AvroRecordConverter.java:159 and trace how the configured Avro reader schema is compared with fields present in the Parquet file. Reproduce the v1-to-v2 read using the compatibility settings from the issue; done means the removed foo field is ignored while bar is read successfully without InvalidRecordException.

Written by the indexing model from the issue text.