[C++] Check nullability when validating fields on batches or struct arrays

[asfimport]

According to ARROW-15899, it is possible to declare a field non-nullable, associate with data that has nulls, and still pass validation.

Validation should instead fail in such a situation (at least full validation, since computing the null count can be O(n)).

Reporter: Antoine Pitrou / @pitrou Assignee: Kaouther Abrougui

Related issues:

• [C++] Parquet writes broken file or incorrect data when nullable=False (relates to)
• [C++] Properly handle non-nullable fields in Parquet reading (is related to)

  PRs and other links:

• GitHub Pull Request #12706

_{Note: This issue was originally created as ARROW-15961. Please see the migration documentation for further details.}

[asfimport]

Antoine Pitrou / @pitrou: cc @AlvinJ15

[asfimport]

Krisztian Szucs / @kszucs: Postponing to 9.0 based on the PR comments.

[asfimport]

Krisztian Szucs / @kszucs: Moving to 10.0 since the PR is in progress.

[asfimport]

Apache Arrow JIRA Bot: This issue was last updated over 90 days ago, which may be an indication it is no longer being actively worked. To better reflect the current state, the issue is being unassigned per project policy. Please feel free to re-take assignment of the issue if it is being actively worked, or if you plan to start that work soon.

[asfimport]

Kaouther Abrougui: I'll continue work on this.