chore(blazor): regenerate NSwag client to fix 204 NoContent handling on delete endpoints

The previous Generated.cs was generated when delete endpoints returned 200 OK.
After adding TypedResults.NoContent() and .Produces(Status204NoContent) to all
delete endpoints, the client must be regenerated so NSwag emits the correct
status code checks.

Changes in Generated.cs:
- RolesDeleteAsync: status_ == 200 -> status_ == 204
- UsersDeleteAsync: status_ == 200 -> status_ == 204
- GroupsDeleteAsync: status_ == 200 -> status_ == 204
- RemoveUserFromGroupAsync: status_ == 200 -> status_ == 204

Generated with: NSwag.ConsoleCore v14.6.3 from https://localhost:7030/openapi/v1.json

Author: César Castro