Signalr version 8.0.5 - If I have even one connected client, shutdown of the app is 30 seconds

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Describe the bug

This is probably a duplicate of https://github.com/dotnet/aspnetcore/issues/53165 . Our application, whenever there is at least one client connected needs 30 seconds from when the Asp.NET core receve the IsClosing from when the app is closed.

This is really annoying because we have software running as windows service, and having this long timeout sometimes generates problem.

We took the timing with IHostedLifecycleService and whenever there is a client connected the time between closing and closed is always 30 seconds (with a difference of max 100 milliseconds).

We are using version 8.0.5, and issue [#53165](https://github.com/dotnet/aspnetcore/issues/53165) is closed so I'm expecting not to have this problem.

### Expected Behavior

When I shutdown my asp.net core application I do not want signalr block the shutdown for 30 seconds, because it causes problem.

I'm expecting also the possibility to force signalr to close everything and letting the application shutdown correctly.

### Steps To Reproduce

I do not have a minimal reproduction, it happens always on our software.

### Exceptions (if any)

_No response_

### .NET Version

8.0.404

### Anything else?

_No response_