fix(ui): Feature/clone freight from history

[kevinetore]

Closes #6517

This PR allows users to reconstruct and clone a historical Freight from a stage's Freight history, even when the original Freight resource has been removed by garbage collection.

Instead of failing when the referenced Freight no longer exists, the UI reconstructs a Freight from the historical Stage data and opens the existing assemble freight workflow. This allows users to modify versions before assembling a new Freight.

[netlify]

✅ Deploy Preview for docs-kargo-io ready!

Name	Link
🔨 Latest commit	85d40a9
🔍 Latest deploy log	https://app.netlify.com/projects/docs-kargo-io/deploys/6a43709a9bb67e0008fc61c6
😎 Deploy Preview	https://deploy-preview-6518.docs.kargo.io
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[kargo-governance-bot]

Automated Policy Notice

This pull request has been converted to a draft because it does not reference an unblocked issue. Maintainers do not routinely review drafts.

All contributions to Kargo require a linked, unblocked issue. This ensures that proposed changes have been reviewed by maintainers before effort is invested.

To move forward:

1. Open a Bug Report or Feature Request
2. Wait for a maintainer to review the issue and remove any blocking labels
3. Update this PR's description, linking to the issue using Closes #<number>
4. Ensure the implementation in this PR is consistent with discussion points in the linked issue
5. Mark the PR ready for review

See the Contributor Guide for full details.

[kargo-governance-bot]

Automated Policy Notice

This pull request has been converted to a draft because it does not reference an unblocked issue. Maintainers do not routinely review drafts.

All contributions to Kargo require a linked, unblocked issue. This ensures that proposed changes have been reviewed by maintainers before effort is invested.

To move forward:

1. Open a Bug Report or Feature Request
2. Wait for a maintainer to review the issue and remove any blocking labels
3. Update this PR's description, linking to the issue using Closes #<number>
4. Ensure the implementation in this PR is consistent with discussion points in the linked issue
5. Mark the PR ready for review

See the Contributor Guide for full details.