Added content-view tests related to redhat content.

Added support to handle even redhat content from manifests, to the
`setup_to_create_cv` function.

Note:- No lifecycle env creation required while publishing.
Can the `Repository.sync` method can be used instead? Also, can the assertion directly below this statement be examined? It doesn't look correct to me. The assertion checks that multiple task IDs are returned, and given my current (admittedly minimal) knowledge of tasks and repository syncing, that doesn't make sense.