Enhance inbound management by removing MaxClients property

- Removed the MaxClients property from Inbound-related data models, including InboundDto and PublishInboundCommand.
- Updated related methods and handlers to reflect the removal of MaxClients, ensuring consistent behavior across the application.
- Adjusted API documentation and frontend components to remove references to MaxClients, streamlining the inbound publishing process.
- Enhanced logging in command handlers to handle node unavailability scenarios during user actions.
- Improved database schema and migrations to align with the updated data model.

docs/api-design.md

@@ -267,7 +267,7 @@ approve/reject над `ActivationRequest`.
 | Метод | Путь                                   | Роль  | Тело запроса                                                              | Тело ответа |
 | ----- | -------------------------------------- | ----- | ---------------------------------------------------------------------------- | ------------- |
 | GET   | `/api/admin/inbounds`                  | admin | query: `nodeId?`                                                             | `InboundDto[]` |
-| PUT   | `/api/admin/inbounds/{id}/publish`     | admin | `{ isPublished, displayName?, allowedRoleIds?, maxClients? }`               | `InboundDto` |
+| PUT   | `/api/admin/inbounds/{id}/publish`     | admin | `{ isPublished, displayName?, allowedRoleIds? }`               | `InboundDto` |
 
 ## Admin — Users & Stats