refactor(android): improve alarm cancellation logging in scheduler

Add detailed logging when cancelling existing alarms to aid in
debugging notification scheduling issues. Logs now indicate whether
an existing alarm was found and cancelled, or if no alarm existed.

This improves observability when investigating duplicate notifications
or scheduling conflicts.

android/plugin/src/main/java/com/timesafari/dailynotification/DailyNotificationScheduler.java

@@ -115,7 +115,9 @@ public class DailyNotificationScheduler {
             Log.w(TAG, "TTL enforcer not set, proceeding without freshness validation");
         }
             
-            // Cancel any existing alarm for this notification
+            // Cancel any existing alarm for this notification ID to prevent duplicates
+            // This ensures only one alarm exists for this notification at a time
+            Log.d(TAG, "Phase 3: Cancelling existing alarm for notification: " + content.getId());
             cancelNotification(content.getId());
             
             // Create intent for the notification
@@ -418,7 +420,9 @@ public class DailyNotificationScheduler {
             if (pendingIntent != null) {
                 pendingIntentManager.cancelAlarm(pendingIntent);
                 pendingIntent.cancel();
-                Log.d(TAG, "Cancelled notification: " + notificationId);
+                Log.d(TAG, "Cancelled existing alarm for notification: " + notificationId);
+            } else {
+                Log.d(TAG, "No existing alarm found to cancel for notification: " + notificationId);
             }
         } catch (Exception e) {
             Log.e(TAG, "Error cancelling notification: " + notificationId, e);