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.Domain/Inbounds/Inbound.cs

@@ -17,7 +17,6 @@ public sealed class Inbound : Entity
     public int Port { get; private set; }
     public bool IsPublished { get; private set; }
     public string? DisplayName { get; private set; }
-    public int? MaxClients { get; private set; }
     public IReadOnlyList<Guid> AllowedRoleIds { get; private set; } = [];
     public DateTimeOffset? LastSyncAt { get; private set; }
 
@@ -52,16 +51,11 @@ public sealed class Inbound : Entity
         LastSyncAt = DateTimeOffset.UtcNow;
     }
 
-    public void Publish(
-        string? displayName,
-        IReadOnlyCollection<Guid> allowedRoleIds,
-        int? maxClients
-    )
+    public void Publish(string? displayName, IReadOnlyCollection<Guid> allowedRoleIds)
     {
         IsPublished = true;
         DisplayName = displayName;
         AllowedRoleIds = allowedRoleIds.Distinct().ToList();
-        MaxClients = maxClients;
     }
 
     public void Unpublish() => IsPublished = false;