[arrow] Update to 5.0.0

[ianmcook]

Updates the arrow port to version 5.0.0

[github-actions]

This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!

After committing all other changes, the version database must be updated

git add -u && git commit
git checkout 8dddc6c899ce6fdbeab38b525a31e7f23cb2d5bb -- versions
./vcpkg x-add-version --all

Diff

diff --git a/versions/a-/arrow.json b/versions/a-/arrow.json
index c8b33d9..64528d5 100644
--- a/versions/a-/arrow.json
+++ b/versions/a-/arrow.json
@@ -1,7 +1,7 @@
 {
   "versions": [
     {
-      "git-tree": "244420f209fd8afcc5f2fd1cc9c536060e75d63a",
+      "git-tree": "53971762b449ee0936e101ef0de0681586664045",
       "version": "5.0.0",
       "port-version": 0
     },

[ianmcook]

The CI failure is happening because tensorflow-cc is not building. I believe this is unrelated to arrow. tensorflow-cc requires Bazel 3.99.0 or lower and this vcpkg commit on July 22 updated Bazel to 4.1.0: 16aeda9#diff-151d9ba93b4be2dfa98ec4f962bd066169262d77d1ae72b256db570329f7d898R399

I opened #19235 for this.

I will add tensorflow-cc:x64-windows-static=fail to scripts\ci.baseline.txt.

[ianmcook]

@GPSnoopy please let me know if you encounter any issues updating ParquetSharp to Arrow 5.0.0

[PhoebeHui]

The tensorflow failures would be fixed by PR #19165

[JonLiu1993]

@ianmcook ，Have you tested the feature locally？

[GPSnoopy]

@ianmcook, all green for me: G-Research/ParquetSharp#214

[ianmcook]

@ianmcook ，Have you tested the feature locally？

Yes, I tested most of the non-default features locally by running both of these:

./vcpkg install arrow[dataset,mimalloc,orc,s3]:x64-windows --recurse
./vcpkg install arrow[dataset,mimalloc,orc,s3]:x64-windows-static --recurse

The jemalloc feature is only relevant for non-Windows environments, and the flight feature of the arrow port is currently experimental and known to have build problems, so I did not test those locally.

[dan-shaw]

The tensorflow baseline failure should have been fixed by #19165. Can we remove the baseline update?

[ianmcook]

The tensorflow baseline failure should have been fixed by #19165. Can we remove the baseline update?

Removed in 478864e