Description of problem:
Although the Life Cycles synchronization when using `hammer capsule content synchronize --id 2 --lifecycle-environment-id 2` is honored, hence right Content is being distributed to the Client Hosts, Satellite GUI wrongly states that all the Life Cycles are in sync.
 

How reproducible:
Always

Is this issue a regression from an earlier version:
No
 

Steps to Reproduce:
Environment:
Satellite:

• Setting `hammer settings set --name foreman_proxy_content_auto_sync --value false`
  Life Cycles:
• devel (id 2)
• production (id 3)
  Content-view:
• version 1.0 contains kernel-4.18.0-513.24.1.el8_9
• version 2.0 conatins kernel-4.18.0-553.34.1.el8_10
  Capsule:
• MyCapsule (id 2)
  Content Host:
• MyHost (registered to MyCapsule on Production Life Cycle)

Innitial Status:

• Devel Life Cycle is at v2.0
• Production Life Cycle is at v1.0

1. Check on Infrastructure > Capsules > MyCapsule
~~~
1 environment(s) can be synchronized: production
~~~
2. Manually sync Devel Life Cycle:
~~~
hammer capsule content synchronize --id 2 --lifecycle-environment-id 2
~~~
3. Check on Infrastructure > Capsules > MyCapsule. I shows Capsule is fully synchronized.
~~~
Capsule is synchronized
~~~
4. Check on a Content Host registered to Production correctly shows kernel-4.18.0-513.24.1.el8_9 as the latest available.
5. Manually sync Production Life Cycle:
~~~
hammer capsule content synchronize --id 2 --lifecycle-environment-id 3
~~~
6. Now the Content Host shows kernel-2.0 4.18.0-553.34.1.el8_10 as available.

Actual behavior:
Satellite wrongly shows Capsule as fully synced after synchronize any Life Cycle although there are still unsynchronized Life Cycles.

Expected behavior:
Satellite should show `1 environment(s) can be synchronized: production` for the Capsule until this Life Cycle is synchronized.