[CI][C++] Resolve ctest failures on VS 2019 builds

[asfimport]

Running ctest on Windows after building the Arrow library with Visual Studio 2019, I regularly see these two tests fail:

• TestStatisticsSortOrder/0.MinMax

• TestStatistic.Int32Extremums

  Logs look like this:

  [ RUN      ] TestStatisticsSortOrder/0.MinMax
  D:/a/crossbow/crossbow/arrow/cpp/src/parquet/statistics_test.cc(670): error: Expected equality of these values:
    stats_[i].min()
      Which is: "\0\0\0\0"
    cc_metadata->statistics()->EncodeMin()
      Which is: "\x3\0\0\0"
  D:/a/crossbow/crossbow/arrow/cpp/src/parquet/statistics_test.cc(838): error: Expected: this->VerifyParquetStats() doesn't generate new fatal failures in the current thread.
    Actual: it does.
  [  FAILED  ] TestStatisticsSortOrder/0.MinMax, where TypeParam = struct parquet::PhysicalType<1> (1 ms)

  [ RUN      ] TestStatistic.Int32Extremums
  D:/a/crossbow/crossbow/arrow/cpp/src/parquet/statistics_test.cc(900): error: Expected equality of these values:
    stats->min()
      Which is: -2147483648
    expected_min
      Which is: 0
  [  FAILED  ] TestStatistic.Int32Extremums (0 ms)

  This happened in the crossbow task test-build-vcpkg-win until I removed ctest from dev/tasks/vcpkg-tests/cpp-build-vcpkg.bat to suppress it: https://github.com/ursacomputing/crossbow/actions?query=branch:actions-99-github-test-build-vcpkg-win

  This also happened when I ran the release verification script dev/release/verify-release-candidate.bat on 4.0.0 RC4 using conda for dependencies.

  Diagnose and resolve these failures.

Reporter: Ian Cook / @ianmcook
Assignee: Antoine Pitrou / @pitrou

Related issues:

• [C++] Add vcpkg.json manifest to cpp project root (relates to)
• [Dev][Wiki][Release] Fix and update Windows RC verify script (is depended upon by)

PRs and other links:

• GitHub Pull Request #10583

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

[asfimport]

Antoine Pitrou / @pitrou:
@ianmcook Can you post a PR to reenable the failing test?

[asfimport]

Ian Cook / @ianmcook:
@pitrou Yes: #10583

[asfimport]

Antoine Pitrou / @pitrou:
Issue resolved by pull request 10583
#10583