Improve Queuing & Paused Account UX

When a client account is paused, the interface currently shows a misleading message indicating that they have reached the maximum number of concurrent requests. Instead, the UI should clearly indicate that the account is paused and offer a clear way to unpause it, which would then activate the next request in the queue. Problem Right now, paused clients appear as if they’ve hit their concurrent request limit. This is confusing for admins/team members, because the real reason nothing is moving is that the account is paused, not that capacity was reached. This makes it harder to understand why the next request in the queue isn’t being started.