Description of problem:

We are running a CV version import ( incremental ) with:

```
hammer content-import version --organization-id=1 --path=/var/lib/pulp/imports/2023-1-28T03-49-03-00-00
```

...but has produced the following errors repeated for several repositories at about 61% of task completion.

Example:

```
duplicate key value violates unique constraint "rpm_updatecollectionname_name_update_record_id_6ef33bed_uniq"
```

This error repeats several times for various RHEL 7,8 and 9 repositories.

Please note that we can NOT provide a sosreport, logs or tracebacks from this customer, and Satellite is running in an air-gapped disconnected environment.

Our support case is https://access.redhat.com/support/cases/#/case/03679066/

There have been other support cases from different customers where this exact database key is reporting an error ( rpm_updatecollectionname_name_update_record_id_6ef33bed_uniq ), and in all of them Red Hat support has recommended that they switch to using the Syncable Exports feature instead of actually resolving the issue.

We are on version 6.11 of Satellite, but it's notable that other support cases indicate that the issue is present on Satellite 6.13 too.

Other support cases that contain the rpm_updatecollectionname_name_update_record_id_6ef33bed_uniq error:
https://access.redhat.com/support/cases/#/case/03671664 ( Sat 6.12 )
https://access.redhat.com/support/cases/#/case/03670822 ( Sat 6.13 )

Version-Release number of selected component (if applicable):
6.11
6.12
6.13

How reproducible:
Create large CV to export/import
After that succeeds, create incremental export and try to import that version of CV

Actual results:
duplicate key value violates unique constraint "rpm_updatecollectionname_name_update_record_id_6ef33bed_uniq"

Expected results:
Incremental Content View imports successfully

Additional info: