Uniformizing booleans naming in ParquetWriter

[hamza-tam]

Make sure you have checked all steps below.

Jira

• My PR addresses the following Parquet Jira issues and references them in the PR title. For example, "PARQUET-1234: My Parquet PR"
  • https://issues.apache.org/jira/browse/PARQUET-XXX
  • In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

Tests

• My PR does not need testing for this extremely good reason: Only variable renaming

Commits

• My commits all reference Jira issues in their subject lines. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters (not including Jira issue reference)
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

Documentation

• In case of new functionality, my PR adds documentation that describes how to use it.
  • All the public functions and the classes in the PR contain Javadoc that explain what it does

[yabola]

Thanks for working on it. Overall looks well. it can help to unify the code style.

But you modified the public variable, which may lead to code forward incompatibility. This may be unacceptable

[shangxinli]

Yeah, public ones are tricky and we need to make it compatible. But overall, this is a great effort to improve our code.

[Fokko]

Unfortunately, we cannot change public static methods, since other projects might be using them. If we want this we first need to deprecate the old values.

[Fokko]

Closing this since we have to go through the deprecation cycle which seems a bit excessive for just a rename