Change conda channel order for Windows builds
- [x] closes #28356
- [ ] tests added / passed
- [x] passes `black pandas`
- [x] passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
- [ ] whatsnew entry

Do we also need the `channel_priority` as part of the config?

https://conda-forge.org/docs/user/tipsandtricks.html#how-to-fix-it
 @xhochy the failure you get in `test_cross_engine_fp_pa` is a known issue (if you have combination of latest released versions of both pyarrow and fastparquet; apparently this is a combination we were not yet testing?) and should be fixed in the upcoming pyarrow release (https://issues.apache.org/jira/browse/ARROW-6492) > Do we also need the `channel_priority` as part of the config?
> 
> https://conda-forge.org/docs/user/tipsandtricks.html#how-to-fix-it

No, we shouldn't need it as it is the default in conda 4.7. > @xhochy the failure you get in `test_cross_engine_fp_pa` is a known issue (if you have combination of latest released versions of both pyarrow and fastparquet; apparently this is a combination we were not yet testing?) and should be fixed in the upcoming pyarrow release (https://issues.apache.org/jira/browse/ARROW-6492)

Cool, that saves me from looking into this. What should I do to work around this? xfail for `pyarrow==0.14.x`?

Also is this is change worth a whatsnew entry? > Cool, that saves me from looking into this. What should I do to work around this? xfail for pyarrow==0.14.x?

Yes, something like that

> Also is this is change worth a whatsnew entry?

Not need if you are OK with that ;) Looks good (doc build failure is unrelated).

@xhochy I think you'll need to remove the WIP flag. @TomAugspurger Done. The docs failure is indeed unrelated (problem with downloading from url) Thanks @xhochy ! @meeseeksdev backport to 0.25.x