Description of problem:

The new bulk repository set management page shows container, ansible, etc repositories that do not benefit from repository set management. Only repositories that are managed by subscription-manager (yum and debian in upstream) need repository set enablement.

The host details repo set management page does not show non-yum (nor non-deb) repositories.

How reproducible:

100%

Is this issue a regression from an earlier version:

If you consider the old bulk repo set management, I think yes.

Steps to Reproduce:

1. Create repos of many types

2. Register a host

3. Look at the bulk repo set management options

Actual behavior:
Container repos, for example, are among the list of repo sets you can enable.

Expected behavior:
Only yum repositories (and deb upstream) should be in the repo set enablement list.

Business Impact / Additional info: