continue removing python2 from CI
Update: Partly superceded by #867, but removes a few more vestigial Python 2 configurations.
Fixes https://github.com/Netflix/metaflow/issues/668; opening partly for discussion.
This may have to wait for Metaflow 3.x; @villelaitila mentioned that long-running Metaflow services may exist where upgrading them (to a new version that removes Python 2), but not their clients, could cause breakage if those clients try to do Python 2 things.
I'm not familiar enough with what services like that may exist, or whether anyone is likely to run into that situation. Interested in others' thoughts!
This was factored out of #612.
bumping this, seems like #867 already did the main work of taking python 2 out of the CI, but there's some additional Python 2 CI configs laying around that this cleans up