no pip2 package provider when pip3 is system default

If the pip command on a puppet client points to the pip3 binary (instead of the more typical pip2), then there is no difference between installing packages with puppet's pip provider vs. the pip3 provider. Consequently, there isn't a clean way to install Python 2 packages on such a client. To resolve this, I would suggest adding a pip2 package provider.