test(fusion_claims,fusion_tasks): fix clone-test failures (future dates + seed-aware asserts)

Real install verified on the Westin clone; these were test-only bugs:
- Task-create tests hardcoded scheduled_date 2026-06-03, now in the past, which
  the base _check_no_overlap rejects ('Cannot schedule tasks in the past'). Use
  future dates (tz test pins a future July date so Toronto stays EDT for the
  9:00->13:00 UTC assertion).
- Service-rate resolver tests created rows with seeded codes (callout_standard_normal,
  per_km) -> UNIQUE(code) violation post-install. Assert against the seed instead.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

fusion_tasks/tests/test_task_tz.py

@@ -21,9 +21,12 @@ class TestTaskTz(TransactionCase):
             'login': 'tz_test_tech_svcbook',
             'x_fc_is_field_staff': True,
         })
+        # A FUTURE date in July so the task is not "in the past" (the base
+        # _check_no_overlap constraint rejects past dates) and Toronto is firmly
+        # in EDT (-4), keeping the 9:00 -> 13:00 UTC assertion deterministic.
         cls.task = cls.env['fusion.technician.task'].create({
             'technician_id': cls.tech.id,
-            'scheduled_date': date(2026, 6, 3),
+            'scheduled_date': date(date.today().year + 1, 7, 1),
             'time_start': 9.0,
             'time_end': 10.0,
         })