ParquetWriter/ParquetReader should parse options directly from supplied Configuration

As a Parquet user, my expectation is that ParquetWriter/ParquetReader will automatically parse any options passed in the supplied Configuration. For example:

```

Configuration conf = new Configuration();
conf.setBoolean(ParquetOutputFormat.BLOOM_FILTER_ENABLED, true);

ParquetWriter writer = AvroParquetWriter.builder(path)
.withSchema(Car.SCHEMA$)
.withConf(conf)
.build();

```

However, the above code results in a ParquetWriter where `bloomFilterEnabled` is set to false-the expected way to configure this is to use `ParquetWriter#withBloomFilterEnabled` directly.

IMO, when `ParquetWriter#withConf` is invoked, it should also delegate to `encodingPropsBuilder` and set any Configured properties.

**Reporter**: [Claire McGinty](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=clairemcginty) / @clairemcginty
#### PRs and other links:
- [GitHub Pull Request #1157](https://github.com/apache/parquet-mr/pull/1157)

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

Commencez par ParquetWriter et ParquetReader, en vous concentrant sur withConf et sur l’option de configuration nommée dans l’exemple, ParquetOutputFormat.BLOOM_FILTER_ENABLED. Examinez GitHub Pull Request #1157 et vérifiez que les valeurs de Configuration fournies sont prises en compte plutôt que d’exiger des options directes du builder.

Rédigé par le modèle d'indexation à partir du texte de l'issue.