Refactor logging messages for consistency and clarity

- Updated various logging messages across the application to replace Russian text with English equivalents, ensuring consistency in error and information logs.
- Enhanced clarity in log messages related to Telegram bot operations, user management commands, and health check services, improving overall traceability and understanding of application behavior.

backend/src/PnvPanel.Api/Telegram/PnvBotUpdateHandler.cs

@@ -36,13 +36,13 @@ public sealed class PnvBotUpdateHandler(
         }
         catch (Exception ex)
         {
-            logger.LogError(ex, "Ошибка обработки Telegram-апдейта {UpdateId}", update.Id);
+            logger.LogError(ex, "Failed to process Telegram update {UpdateId}", update.Id);
         }
     }
 
     public Task HandleErrorAsync(ITelegramBotClient botClient, Exception exception, HandleErrorSource source, CancellationToken cancellationToken)
     {
-        logger.LogError(exception, "Ошибка Telegram-бота (источник {Source})", source);
+        logger.LogError(exception, "Telegram bot error (source {Source})", source);
         return Task.CompletedTask;
     }
 

backend/src/PnvPanel.Api/Telegram/TelegramBotHostedService.cs

@@ -21,7 +21,7 @@ public sealed class TelegramBotHostedService(
     {
         if (string.IsNullOrWhiteSpace(options.Value.BotToken))
         {
-            logger.LogWarning("Telegram__BotToken не задан — бот не стартует.");
+            logger.LogWarning("Telegram__BotToken is not set — bot will not start.");
             return;
         }
 
@@ -31,7 +31,7 @@ public sealed class TelegramBotHostedService(
             DropPendingUpdates = true,
         };
 
-        logger.LogInformation("Telegram-бот запускается (long polling)...");
+        logger.LogInformation("Telegram bot starting (long polling)...");
 
         try
         {