Description of problem: when registering a system using an activation key and a custom product I cannot easily attach to content.
For eg if I have an epel product and a server activation key I cannot use the activation key for multiple server versions because epel 6 repos will attach to 7 hosts and vice versa. This means I either need to have different products/activation keys for epel (6epel, 7epel) and make smaller scoped activation keys (--activationkey server,7epel,7custom) or I have to make special activationkeys that contain the version/product and somehow manage licenses available in each key. With that example I would still make products for each epel version but then in the activation key automatically place the correct product and split available entitlements between a 6server and 7server activation key.
The problem also comes up when specifying architecture per repo (6epelx86?)

How reproducible: Always

Steps to Reproduce:
1. Make a custom product with content for different OS releasever and architecture
2. create an activation key that uses that product
3. subscribe a machine to the activation key

Actual results:
Servers attempt to auto attach to the incorrect release of products

Expected results:
Servers would only attach to products of their releasever and arch