Zabbix 6 - Modifying triggers causes a "petmypid() has been disabled for security reasons" message.

Summary: We previously had Zabbix 5 running without any issue.  I recently updated to Zabbix 6.0.4 and while everything works, I get an error message displayed whenever I modify triggers.  This is a new behavior that is unexpected.

To be clear, the triggers seem to be successfully modified and work, we're just unsure why we're getting this error.

The error is documented in the attached screenshot.

Steps to reproduce:

1. Modify existing trigger, click save.

Result:
See screenshot...

Expected:
Trigger modified without any "getmypid()" messages.