`Package` resource naming clash if same named `Package` exists in multiple `CatalogSource`s

[everettraven]

Currently the CatalogSource controller creates Package resources when reconciling a CatalogSource CR. It doesn't do any special naming logic to ensure uniqueness of Package resources being created which means that if multiple catalogs define a package of the same name (but are technically different), there will be a naming clash resulting in an error creating the corresponding Package resource.

We should evaluate what our options are to prevent this naming clash.

One suggestion is to see what options we have to specify the Package admission criteria on our custom apiserver. For more context see: #1 (comment)

[anik120]

This is probably not going to be an issue if we configure labels as discussed in #38. Multiple catalogs can include packages with the same name, but clients would have to distinguish between those packages by specifying the catalog they want the package from.

I.e kubectl get catalogmetadata -l package=foo,catalog=bar