feat: use restore plans in snapshot restore UI

[nicotsx]

The restore routes and form should render from the same target-scoped
plan the server uses for execution. That keeps the client from guessing
the snapshot base, detecting Windows paths, or deciding original/custom
availability itself

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 614daa73-c83f-4b74-9c18-fe809753cd87

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[nicotsx]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• ci: run restore integration checks #1025
• feat: use restore plans in snapshot restore UI #1024 👈 (View in Graphite)
• feat: expose snapshot restore planning API #1023
• feat: plan restores at execution target #1022
• refactor: add snapshot path context facade #1021
• fix: harden volume browser path codec #1020
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.