Description of problem:

When a "yum --help" or other trivial yum calls are executed using the subscription-manager plugin, by default it makes two calls up to the Subscription-Manager source. Satellite is the main concern, but it could be the Red Hat portal as well.

Version-Release number of selected component (if applicable):

How reproducible: Always

Steps to Reproduce:
1. tail -f /var/log/foreman/production.log on the Satellite
2. execute "yum --help" on a Content Host.
3. Observe calls to ...
GET "/rhsm/" for the Content Host IP
GET "/rhsm/consumers/<UUID>/content_overrides for IP
GET "/rhsm/consumers/<UUID>/release for IP

Actual results:

Even a call like "yum --help" makes multiple upcalls to the subscription-manager source, when likely it is unneccessary.

Expected results:

yum's subscription-manager plugin should only contact the subscription-manager source when necessary.

Additional info:

"yum --help" is the most extreme example of uneccesrary upcalls, but ideally the plugin would not upcall to the Satellite if it doesn't need to, like when listing local package, repo, information.

One more note, of the three observed calls above, the "GET /content_overrides" can be stopped by setting "full_refresh_on_yum = 0" in /etc/rhsm/rhsm.conf, but that may be overkill. In some use cases you do want yum to do the full refresh when you actually make a change, but it shouldn't necessarily be done for local queries on the client.