Description of problem:
If user triggers an optimized Capsule sync manually after publishing/promoting a content view containing docker repositories. The capsule sync task doesn't sync anything.

How reproducible:
Easy

Steps to Reproduce:
1. Set "Sync Capsules after content view promotion" to No
2. Create and sync a docker repository.
~~~
Registry URL: https://registry-1.docker.io/
Upstream Repository Name: library/hello-world

1. Limit the tag to sync
   Include Tags: latest
   ~~~

3. Create a content view and attach the docker repository to it. Publish and promote the content view.
4. Trigger a optimized capsule sync to sync the CV repositories for the first time to the Capsule.
5. In the docker repository page, include a new tag and sync it.

Include Tags: latest, linux

6. Publish and promote new version of the content view.
7. Trigger a optimized capsule sync again

Actual results:
The optimized capsule sync doesn't sync newly published docker repositories

Expected results:
Optimized capsule sync should sync the newly published docker repositories.

Additional info:
This is because the smart proxy sync history of the docker repositories didn't get clear after publishing/promoting the content view.