Support: Increase startup limit interval for Puma and Sidekiq

Both Puma and Sidekiq are systemd services of type notify, which means that they
notify systemd once they have started. If they run into the startup timeout,
they will be restarted, but they will neer hit their start limit burst
threshold, since the window is smaller than their startup timeout times the
number of startups (DefaultStartLimitBurst=5).

This commit increases the start limit interval so that the service can fail when
repeatedly running into the startup timeout instead of being constantly
restarted.

lib/support/systemd/gitlab-puma.service

@@ -4,7 +4,7 @@ Conflicts=gitlab.service
 ReloadPropagatedFrom=gitlab.target
 PartOf=gitlab.target
 After=network.target
-StartLimitIntervalSec=100s
+StartLimitIntervalSec=11min
 
 [Service]
 Type=notify

lib/support/systemd/gitlab-sidekiq.service

@@ -4,6 +4,7 @@ ReloadPropagatedFrom=gitlab.target
 PartOf=gitlab.target
 After=network.target
 JoinsNamespaceOf=gitlab-puma.service
+StartLimitIntervalSec=11min
 
 [Service]
 Type=notify