Fixes #6027 - Made product gpg update more secure

It is possible via api to associate gpg key belonging to a different
org to product.

This commit checks for gpg key readable + gpg key org association before
accepting the provided gpg key.
Fixes #6050 - Better error message on filter rules create

Basically cli did this on filter rule create with no filter rule params
specified.

$ hammer  content-view filter rule create --content-view-id=4
--organization-id=1 --content-view-filter-id 1

Could not create the filter rule:
  Error: 400 Bad Request

This commit fixes that by giving more context on what needs to be
specified. This is slightly tricky because depending on errata or
package filters the "base" field requirement is bound to change. Here
are the 2 scenarios this fix now handles..
1) On a package filter specifying package rule it raises name cant be
blank.

$ hammer  content-view filter rule create --content-view-id=4
--organization-id=1 --content-view-filter-id 1

Could not create the filter rule:
  Validation failed: Name can't be blank

2) On an erratum filter specifying erratum rule it raises something else

$ hammer  content-view filter rule create --content-view-id=4
--organization-id=1 --content-view-filter-id 2
Could not create the filter rule:
  Validation failed: Invalid erratum filter rule specified, Must specify
at least one of the following: 'errata_id', 'start_date', 'end_date' or
'types'
fixes #6064 - fixes content view filter not honoring the name parameter, BZ 1102451
Merge pull request #4212 from parthaa/cv-filter-rule

Fixes #6050 - Better error message on filter rules create
Merge pull request #4198 from parthaa/product-gpg

Fixes #6027 - Made product gpg update more secure
Merge pull request #4216 from cfouant/content-view-filter-by-name

fixes #6064 - fixes content view filter not honoring the name parameter, BZ 1102451