Close out migration for libarrow190

[regro-cf-autotick-bot]

This PR has been triggered in an effort to close out the migration for libarrow190.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

---

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/12925715936 - please use this URL for debugging.}

[conda-forge-admin]

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/meta.yaml) and found it was in an excellent condition.

[xhochy]

Not done.

[h-vetinari]

There's also a feedstock that probably won't move on unless arrow fixes apache/arrow#45283 (we could still close the migration and they just skip arrow v19 of course)

[h-vetinari]

Not done.

I think the migrator is happy as soon as all PRs have been opened (not saying that's good or bad, just an observation). Realistically only csp (see above) and conda-forge/turbodbc-feedstock#147 are missing; conda-forge/river-ingester-feedstock#33 has been pretty dead (the feedstock, I mean).

[xhochy]

I think the migrator is happy as soon as all PRs have been opened

🤔 That behaviour was different in the past. If we merge this, people are forced onto the new library even if some of the builds will take a while.