NGX-380: Always trigger apache/php-fpm restart handlers

[combssm]

• Certain circumstances cause the playbook to apply changes without restarting the service. Subsequent runs do not apply any changes, so the service is again not restarted. This can cause service to be stuck in running state with outdated configs which playbook can not correct. For this reason, we notify the apache, php-fpm, and nginx restart handlers on every run.