[8.0.x] Feature sync with main & upstream

[h-vetinari]

Combination of #853 & #848 for 8.0.x

I double-checked when the features (enabled in a807519) landed:

• 6.0: apache/arrow@1d139fe
• 8.0: apache/arrow@4e1ba57
• 9.0: apache/arrow@7b5912d

However, despite ARROW_GCS seemingly landing in 9.0, it was enabled here in #677 during the 7.0 cycle.

CC @xhochy @pitrou @kkraus14

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[h-vetinari]

@conda-forge-admin, please rerender

[h-vetinari]

So I don't fully get the relationship between gandiva & jemalloc (there should be none?), but in any case, this works if I backport apache/arrow@2c87e81, or presumably I could kick out 6f78775

Any preferences which approach I should take? If it were up to me, I'd backport the jemalloc version bump (& gandiva enablement) back until 6.0.x.

WDYT @xhochy @pitrou @kkraus14?

[kkraus14]

I'd be more in favor of backporting apache/arrow@2c87e81

[h-vetinari]

I'd be more in favor of backporting apache/arrow@2c87e81

There are now passing builds (with the same approach) for 7.0.x and 6.0.x as well. Key part being the gandiva enablement on osx-arm back to 6.0

[h-vetinari]

@conda-forge/arrow-cpp

If someone has concerns / objections to backporting gandiva-on-osx-arm & a jemalloc bump (also mostly for osx-arm) back to all supported versions in conda-forge (until 6.0.x), please let me know.

In case there are no further comments, I'll merge this & #863 & #864 on the weekend.

PS. These PRs also contain some further clean-ups & make the branches consistent (as much as possible/reasonable) with main resp. apache/arrow#14102

[kkraus14]

LGTM, but I'm technically not a maintainer on this recipe 😆