Rename underscore-prefixed validation sample fields

[Copilot]

PR #662 introduced underscore-prefixed private fields in Blazor validation docs samples, which conflicts with the sample convention of camelCase field names without leading underscores.

• Field naming

  • Renamed _messages to messages in the .NET 11 async validation samples.
  • Renamed _remoteErrors to remoteErrors and _accepted to accepted in the remote validation form.
  • Updated all Razor markup and C# references for the renamed fields.

• Scoped cleanup

  • Left framework/path identifiers such as _Imports and _framework unchanged.
  • Renamed a local tuple variable to avoid shadowing the new messages field name.

Example:

<CustomValidation @ref="remoteErrors" />

@if (accepted)
{
    <p id="accepted" role="status">The server accepted the form.</p>
}

[Copilot]

Copilot review overview

🟢 Approval recommended

No unresolved review issues were identified.

Review effort: Lite
Findings: None

What changed in this PR

Renames underscore-prefixed fields in .NET 11 Blazor validation samples to match naming conventions without changing behavior.

Changes:

• Renamed validation message stores.
• Renamed remote validation fields to remoteErrors and accepted.
• Updated references and avoided tuple-variable shadowing.

File	Description
11.0/​BlazorWebAppRemoteValidation/​BlazorWebAppRemoteValidation.Client/​Pages/​Home.razor	Renames remote validation state fields and references.
11.0/​BlazorWebAppRemoteValidation/​BlazorWebAppRemoteValidation.Client/​CustomValidation.razor	Renames the validation message store and tuple variable.
11.0/​BlazorSample_BlazorWebApp/​Components/​UsernameUniquenessValidator.razor	Renames the async validation message store.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.