The ostree deploy was missing the remote in the refspec. This would
lead to a deployment not tracking any remote breaking upgrades.

This could be desired in the future, which we can then explore adding as
a distinct feature with it's own logic.

E.g. if an image is built without a remote in mind, designed for local
updates, this can be used to only track the local repos state for
upgrades.