Force existing non-latest deployments back to latest

[titanous]

When a RestateDeployment is rolled back to a version whose deployment record still exists but is no longer latest, re-register it with force=true. This makes rollback converge instead of reusing an old deployment ID while a newer version remains latest. The decision distinguishes existing latest, existing non-latest (active or inactive), and missing records, with focused unit coverage. The registration request path is shared by ReplicaSet and Knative modes.

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}