CI: Install pyarrow-core instead of pyarrow from conda-forge

[weiji14]

Description of proposed changes

Reduce unnecessary optional dependencies when installing pyarrow from conda-forge. Xref conda-forge/pyarrow-feedstock#111

From https://github.com/conda-forge/pyarrow-feedstock/blob/381a88b6f8957204e34047151c4ca8a3f1e54204/recipe/meta.yaml#L157-L164, this means we won't be installing libarrow-acero, libarrow-dataset, libarrow-substrait and libparquet.

Fixes #

Preview:

Reminders

• Run make format and make check to make sure the code follows the style guide.
• Add tests for new features or tests that would have caught the bug that you're fixing.
• Add new public functions/methods/classes to doc/api/index.rst.
• Write detailed docstrings for all functions/methods.
• If wrapping a new module, open a 'Wrap new GMT module' issue and submit reasonably-sized PRs.
• If adding new functionality, add an example to docstrings or tutorials.
• Use underscores (not hyphens) in names of Python files and directories.

Slash Commands

You can write slash commands (/command) in the first line of a comment to perform
specific operations. Supported slash command is:

• /format: automatically format and lint the code

[seisman]

Also need to update line 82.

Do we also want to update doc/install.md?

[weiji14]

Good catch, done in commits 3e59046 and 0cef357

[seisman]

Aslo need to note that pyarrow-core is available since pyarrow v16 (released in April, 2024). Installing pyarrow-core in ci_tests_legacy.yaml may cause issues in #3639 (comment).

[weiji14]

Aslo need to note that pyarrow-core is available since pyarrow v16 (released in April, 2024). Installing pyarrow-core in ci_tests_legacy.yaml may cause issues in #3639 (comment).

Yes, thanks for the reminder, I think we can use pyarrow-core here, and I'll revert to using pyarrow in #3639. That PR is still a little experimental. Edit: Actually, #3639 is installing pyarrow from PyPI (via uv) instead of conda-forge, so it doesn't really matter.