fix(webapp): preserve complete practice feedback responses

[FelixTJDietrich]

Description

Hardens the practice-group feedback flow introduced by #1487. A dispute is now submitted only when its required explanation is available, and a failed request keeps the complete response ready for retry instead of dropping the dispute resolution.

Practice and expanded-observation selections are also stored in validated URL search parameters. Refreshing or sharing the page preserves its context, while Back and Forward move through selection changes as expected.

This review follow-up also removes redundant implementation commentary from the new profile components and corrects the API migration guidance with the retired endpoint, replacement method and path, and request-field mapping.

How to test

1. Open your own practice-group page and expand feedback that has no existing explanation.
2. Select Disputed. Confirm that the explanation becomes required and no request is sent yet.
3. Enter an explanation and save it. Confirm that one request contains the resolution, explanation, and any existing usefulness response.
4. Simulate a failed save and retry. Confirm that Disputed remains selected and the retry sends the same complete response.
5. Open feedback that already has an explanation and select Disputed. Confirm that it can be submitted immediately without losing the existing explanation or usefulness response.
6. Select a practice and expand an observation. Refresh the page, open its URL in another tab, and use Back and Forward; confirm that each view restores the expected selection.

Automated verification:

pnpm run format
pnpm run check
pnpm run test:webapp
pnpm --filter webapp run build

Checklist

• My changeset summary reads as an operator/user-facing note (it becomes the changelog entry) — see .changeset/README.md
• If operators must act, the changeset and migration entry give actionable upgrade instructions
• I did not commit generated-artifact changes that this PR did not cause

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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: defaults

Review profile: CHILL

Plan: Team

Run ID: bd5ee225-16c4-46df-b186-2f236a44ed5b

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.}

[github-actions]

📚 Documentation Preview

Preview has been removed (PR closed)

[github-actions]

🧩 Storybook Preview

Preview has been removed (PR closed)

[github-actions]

Approved automatically: @FelixTJDietrich is listed in the REVIEW_POLICY_MAINTAINERS repository variable, which the repository treats as satisfying the review requirement. See the review policy in docs/contributor/ci-cd.mdx.