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.

backend/src/PnvPanel.Api/Endpoints/InboundEndpoints.cs

@@ -40,8 +40,7 @@ public static class InboundEndpoints
             id,
             body.IsPublished,
             body.DisplayName,
-            body.AllowedRoleIds ?? [],
-            body.MaxClients
+            body.AllowedRoleIds ?? []
         );
         var result = await sender.Send(command, cancellationToken);
         return result.ToHttpResult();
@@ -51,6 +50,5 @@ public static class InboundEndpoints
 public sealed record PublishInboundBody(
     bool IsPublished,
     string? DisplayName,
-    IReadOnlyList<Guid>? AllowedRoleIds,
-    int? MaxClients
+    IReadOnlyList<Guid>? AllowedRoleIds
 );