Let workflows move cards by start date instead of due date

Each workflow now has a trigger date (due or start): the runner compares
either the card's due date or its start date against now, read straight
from Deck's Card entity. Mails and Nextcloud notifications say whether
the card was overdue or reached its start date. Cards without the chosen
date stay put.

Deck only has a start date since 1.18 and Entity getters are magic, so
DeckIntegrationService::supportsStartdate() checks the property; without
it the form rejects start-date workflows and the runner skips them
without disabling them.

WorkflowRunner::isOverdue() becomes hasPassed(), as it now covers both
dates. Existing workflows keep the due date (migration Version1005).
Bumps to 35.4.0 so the migration runs.

lib/Notification/Notifier.php

@@ -7,6 +7,7 @@ namespace OCA\WorkflowDeckAutomation\Notification;
 use OCA\WorkflowDeckAutomation\AppInfo\Application;
 use OCA\WorkflowDeckAutomation\Service\NotificationMailer;
 use OCA\WorkflowDeckAutomation\Service\NotificationPusher;
+use OCA\WorkflowDeckAutomation\Service\TriggerDate;
 use OCP\IURLGenerator;
 use OCP\Notification\INotification;
 use OCP\Notification\INotifier;
@@ -95,7 +96,12 @@ class Notifier implements INotifier {
 		self::setText(
 			$notification,
 			'{deck-card} wurde nach {target-stack} verschoben',
-			'Die Karte auf {deck-board} ist überfällig und wurde automatisch von {source-stack} nach {target-stack} verschoben.',
+			sprintf(
+				'Die Karte auf {deck-board} %s und wurde automatisch von {source-stack} nach {target-stack} verschoben.',
+				// Missing on notifications from before the start date existed,
+				// which were all about due dates.
+				TriggerDate::describeReason((string)($params['triggerDate'] ?? TriggerDate::DUE)),
+			),
 			$objects,
 		);
 	}