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.

Dockerfile

@@ -37,6 +37,10 @@ ENV ASPNETCORE_ENVIRONMENT=Production \
     ASPNETCORE_HTTP_PORTS=8080
 EXPOSE 8080
 COPY --from=backend /app/publish ./
+# Data Protection key-ring и загрузки тикетов монтируются сюда volume'ами (см. docker-compose.yml).
+# Готовим права заранее — Docker скопирует владельца/содержимое в volume при первом маунте (copy-up).
+RUN mkdir -p /app/keys /app/uploads && chown -R app:app /app/keys /app/uploads
+USER app
 HEALTHCHECK --interval=15s --timeout=5s --start-period=20s --retries=5 \
     CMD curl -f http://localhost:8080/health || exit 1
 ENTRYPOINT ["dotnet", "PnvPanel.Api.dll"]