Use candlepin.service in foreman startup ordering

Foreman depends on Candlepin being fully initialised before it can
serve requests reliably. Without this ordering, foreman.service starts
simultaneously with candlepin.service, competing for CPU and disk I/O
during the JVM startup. This pushes Rails loading time close to the
default TimeoutStartSec (90s) and causes intermittent failures on
restart, particularly when the system is under load.

Because candlepin.service already declares:
  After=redis.service postgresql.service

the transitive ordering becomes:

  postgresql --+
               +--> candlepin --> foreman
  redis -------+

so explicit redis.service and postgresql.service dependencies on
foreman.service are not needed.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: pablomh

src/roles/foreman/tasks/main.yaml

@@ -126,8 +126,8 @@
         WantedBy=default.target foreman.target
         [Unit]
         PartOf=foreman.target
-        Wants=redis.service postgresql.service
-        After=foreman.target redis.service postgresql.service
+        Wants=redis.service postgresql.service candlepin.service
+        After=foreman.target redis.service postgresql.service candlepin.service
   notify: Restart foreman
 
 - name: Deploy Dynflow Container