feat(afk.py): enhance logging for AFK expiration handler

Add debug logs to indicate when the AFK expiration check is skipped
due to maintenance mode and when it is actively running. Log the
absence of expired AFK entries for better traceability. Additionally,
log when the AFK expiration handler starts, providing clarity on its
execution schedule. These changes improve the observability and
debugging capabilities of the AFK expiration process, making it easier
to monitor and troubleshoot.

Author: kzndotsh

src/tux/modules/utility/afk.py

@@ -418,15 +418,19 @@ async def handle_afk_expiration(self) -> None:
         """Check AFK database at a regular interval, remove AFK from users with an entry that has expired."""
         # Skip AFK expiration processing during maintenance mode
         if self.bot.maintenance_mode:
+            logger.debug("Skipping AFK expiration check (maintenance mode)")
             return
 
+        logger.debug("Running AFK expiration handler")
         for guild in self.bot.guilds:
             expired_entries = await self._get_expired_afk_entries(guild.id)
 
             if expired_entries:
                 logger.info(
                     f"Processing {len(expired_entries)} expired AFK entries in {guild.name}",
                 )
+            else:
+                logger.debug(f"No expired AFK entries found in {guild.name}")
 
             for entry in expired_entries:
                 # Re-check if entry still exists (could have been removed by user message)
@@ -468,6 +472,7 @@ async def handle_afk_expiration(self) -> None:
     async def before_handle_afk_expiration(self) -> None:
         """Wait until the bot is ready."""
         await self.bot.wait_until_ready()
+        logger.info("AFK expiration handler started (runs every 120 seconds)")
 
     @handle_afk_expiration.error
     async def on_handle_afk_expiration_error(self, error: BaseException) -> None: