Description of problem:
Katello doesn't create a new publication for default organization repos when importing a content view version with new contents

Steps to Reproduce:

On the connected Satellite:
1. Create a custom repo and upload 1 rpm to it.
2. Create a content view and attach the custom repo.
3. Publish content view version 1.0.
4. Export content view version 1.0
 
hammer content-export complete version --organization-id 1 --content-view-id <cv id> --lifecycle-environment Library --version 1

5. Upload 1 new rpm to the custom repo
6. Publish content view version 2.0
7. Export content view version 2.0

hammer content-export complete version --organization-id 1 --content-view-id <cv id> --lifecycle-environment Library --version 2

8. Copy the exported files to the disconnect Satellite.


On the disconnected Satellite:
9. Import content view version 1.0

hammer content-import version --organization-id 1 --path /var/lib/pulp/imports/<cv version 1 export files path>

10. Register a client to the disconnected Satellite and enable the custom repo then run yum to inspect the repo. The repo should have only 1 rpm.

yum clean all
yum repolist -v

11. Import content view version 2.0
12. Go back to the client and inspect the repo again.

yum clean all
yum repolist -v


Actual results:
Still getting 1 rpm


Expected results:
Should get 2 rpms


Additional info:

The first import task has the following actions but they are not in the 2nd import task:
64: Actions::Pulp3::Repository::CreatePublication (success) [ 0.89s / 0.31s ]
66: Actions::Pulp3::Repository::SavePublication (success) [ 0.03s / 0.03s ]

The following command doesn't solve the issue:

hammer content-view version republish-repositories --content-view-id 1 --version 1.0 --force yes


The repo can be fixed by forcing the publication:

foreman-rake console
Katello::Repository.where(id: [<default org repo id>], library_instance_id: nil).each {|repo| ForemanTasks.async_task(Actions::Katello::Rep
ository::MetadataGenerate, repo, force_publication: true) }
exit