IaaS Discovery - resource update is not reflected in sync

If a cloud resource is updated - ie, tags or IP address or ports change - after the first sync, then we ignore the updates.

Instead, we should look for updates even after the first sync.

No files or tests are named. Start by locating the IaaS discovery and sync entry points, then reproduce a second sync after changing a resource's tags, IP address, or ports. Done means updates made after the first sync are detected and reflected rather than ignored.

Written by the indexing model from the issue text.