Capsule happily syncs when invalid environment requested
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1125397
Description of problem:
Assuming a capsule (id:1) has only the dev (id:2) lifecycle environment attached, attempting to perform a synchronize with the prod (id:4) lifecycle environment will attempt to perform the synchonize.
hammer capsule synchronize --id 1 --environment-id 4
the server will attempt to sync environment 4, even if it is not associated with the capsule
the server should return an error to the user indicating that it is an invalid environment
fixes #6871 / BZ 1125397 - capsule - add error case for content sync
If the user attempts to sync a lifecyle environment that isn't attached
to the capsule, generate an error to the user.