Is your feature request related to a problem? Please describe.

I am wondering if JCSDA is still using jedi-tools-env. Back in the days when I was at JCSDA, we used jedi-tools-env to run some of the GitHub admin jobs, for example managing labels across GitHub repositories, collecting GitHub statistics, ...

I don't recall exactly for which of these tasks, but I had to add a +excel variant to py-pandas for one of them. Now, the +excel variant is becoming problematic, since newer versions of py-pandas require py-python-calamina -> py-maturin -> rust as dependencies. This is the full rust, not just rust-bootstrap. And py-maturin doesn't compile with Intel Classic or Intel LLVM either.

Describe the solution you'd like

If we don't need it anymore, I'd like to get rid of the +excel variant for py-pandas. Even better, if jedi-tools-env is no longer needed (maybe/hopefully @eap is handling all of these tasks differently with Terraform nowadays?), I'd like to get rid of it entirely.

If none of this is possible, then we should modify the common package definitions such that the +excel variant is only used with the GCC compiler (which is also the only compiler that triggers the build of jedi-tools-env).

Additional context

See #831 (comment) for the PR that added the +excel variant.