refactor: reduce notification spam and focus on deployment alerts

- Remove login success notifications (only log to file)
- Remove login failure notifications (only log to file)
- Add deployment completion notification
- Add error notifications for server crashes
- Notifications now only on critical events (deploy/error)

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

TaxBaik.Web/Services/AuthService.cs

@@ -52,16 +52,12 @@ public class AuthService
         if (!BCrypt.Net.BCrypt.Verify(password, user.PasswordHash))
         {
             _logger.LogWarning("로그인 시도: 잘못된 비밀번호 '{Username}'", username);
-            await _telegramService.SendErrorAsync(
-                "로그인 실패",
-                $"사용자: {username}\n실패 사유: 잘못된 비밀번호");
+            // 실패한 로그인은 알림하지 않음 (로그만 남김)
             return null;
         }
 
         _logger.LogInformation("로그인 성공: {Username}", username);
-        await _telegramService.SendInfoAsync(
-            "관리자 로그인",
-            $"사용자: {username}");
+        // 로그인 알림은 제거 (로그만 남김)
         await _adminUserRepository.UpdateLastLoginAtAsync(user.Id);
         return GenerateTokenPair(user);
     }