Skip tagging when there are no new versions

Currently, autodeploy creates tags on every scheduled job even if there are no new versions in the components. We should avoid this redundant behavior by comparing current versions to the last versions before creating tags.