Description of problem:
ISS export sync is completely CLI driven. It is not easy to perform the export and import workflow for an ISS export sync. This is especially true for incremental exports since there is a temporal requirement.

Version-Release number of selected component (if applicable):
All versions.

How reproducible:
Always

Steps to Reproduce:
Suppose you perform a full export sync of a content view. Import this into a downstream server. Next, publish a new version of the content view on the upstream server. The next steps for performing an export sync are not clear or documented.

Furthermore, assume that additional exports have been performed. One would have to know that the incremental operation is only successful if you perform an incremental export relative to the last successful import into the downstream server.

Internal Slack discussion here: https://redhat-internal.slack.com/archives/C04T3JZ5W8K/p1713536715208079

Actual results:
It's not easy to use ISS export sync.

Expected results:
It shouldn't be this hard.

Additional info:
https://redhat-internal.slack.com/archives/C04T3JZ5W8K/p1713536715208079