Add thread-safe locking to request logging in BlazorWebWasm

[Copilot]

Description

Addresses feedback on #123388 regarding thread safety of the requestLogs List in the BlazorWebWasm test asset. The List was being accessed concurrently from multiple HTTP requests without synchronization, causing potential race conditions.

Changes

Added locking around all requestLogs access points:

• Lock object: Introduced requestLogsLock for synchronization
• Middleware Add(): Protected with lock in the logging middleware
• GET endpoint: Returns ToList() snapshot under lock
• DELETE endpoint: Protects Clear() operation with lock

varrequestLogs=newList<BlazorWebWasmRequestLog>();varrequestLogsLock=newobject();app.Use(async(context,next)=>{awaitnext.Invoke();varlogEntry=newBlazorWebWasmRequestLog(/*...*/);lock(requestLogsLock){requestLogs.Add(logEntry);}});app.MapGet("/request-logs",()=>{lock(requestLogsLock){returnrequestLogs.ToList();}});

Testing

No additional testing required - thread safety fix for existing functionality.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.