Test more packages' latest builds in upstream ci

[Sevans711]

Closes #1785

Overview

Adds geoviews (and more other packages, too) to the upstream ci job (via install-upstream.sh). Using the latest geoviews should be sufficient to fix #1785; the upstream ci is failing because it is testing the latest geoviews release (which is not compatible with the latest cartopy; see #1780) when it probably should be testing the latest version of geoviews instead (where a fix has already been merged; see holoviz/geoviews#884).

Closing the original issue only requires adding geoviews to the upstream ci job, but this PR adds more packages there, too. There have recently been other bugs related to the latest versions of packages including breaking changes (see, e.g., #1542, where some cartopy<0.26 plots don't work properly with matplotlib>=3.11). Including more packages in upstream ci may help spot this before the relevant releases actually occur.

Minor sidenote: moved the pip uninstall packages at start of install-upstream.sh into the conda remove command, because they were both being installed by conda. This comes from upstream-dev-ci.yml which uses ci/environment.yml which does not have a pip: ... block; everything there is installed via conda; confirmed by looking at the conda list output from an actual CI Upstream run (e.g.: https://github.com/UXARRAY/uxarray/actions/runs/35949787277/job/107475635076).

(Tiny sidenote: woops, misspelled the branch name! Fixing it means deleting the PR, though, so that typo is here to stay....)

PR Checklist

General

• An issue is created and linked
• Added appropriate labels (if your uxarray repo permissions allow it)
• Filled out Overview and Expected Usage (if applicable) sections

Testing & Benchmarking

• There is adequate test coverage of changes from this PR (add new tests if needed)
  • (Upstream CI workflow shows tests pass when run on this branch, see: https://github.com/UXARRAY/uxarray/actions/runs/36005027889/job/107650878616)
• [N/A] If this PR could affect performance, ran ASV benchmarks and confirmed they show expected behavior (add a new benchmark if necessary)

Documentation and Examples

• [N/A] Docstrings updated with any function changes, and included in all new functions
• [N/A] User (public) functions added to docs/api.rst; internal (private) function names start with an underscore (_)
• [N/A] If touched any notebook files, cleared the output of all cells before committing
• [N/A] If added new notebook files, put into appropriate directories and referenced in appropriate files

AI Disclosure

AI Usage: GitHub Copilot's inline code suggestions, plus asked claude about how to decide whether packages belong in the conda remove or pip uninstall block.

• I have tested and take responsibility for all AI-generated content in my PR.