(PUP-9727) Reduce specificity of gem, pip providers

[gimmyxd]

Due to the recent changes on package providers, when
no default package provider is explicitly set it will
always fallback to gem/puppet_gem/pip/pip3 because of the way
that specificity is calculated for a system which does
not have a default(the match expresion and number of ancestors)

Since those are specific language package managers,
their specificity was lowered to 1 if none of those providers
are set as default provider, otherwise the specficity
is calculated like it was before.

[puppetcla]

CLA signed by all contributors.

[gimmyxd]

ad hoc build: https://jenkins-master-prod-1.delivery.puppetlabs.net/view/Adhoc/job/platform_puppet-agent-extra_puppet-agent-integration-suite_adhoc-ad_hoc/602/

There are some errors which do not seem related to the package providers changes

[joshcooper]

The debian puppet failure is due to PUP-9564

[joshcooper]

I had some concerns about changing the specificity of gem and pip providers, as it feels like a breaking change. But as far as I'm aware, none of those providers are the default for any platform. So it's unlikely that:

package { 'something': }

Would have ever worked for gem/pip/etc. In other words, people would have had to specify the provider explicitly, and this PR doesn't change that behavior.