fix: objc[32080]: +[__NSCFConstantString initialize] may have been in…

[strophy]

… progress in another thread when fork() was called.

Issue being fixed or feature implemented

Running deploy under macOS results in the error:

TASK [dashmate : Check SSM parameter store for ZeroSSL certificate ID] ******************************************************************************************************************************************
objc[32080]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[32079]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[32080]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
objc[32079]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
ERROR! A worker was found in a dead state

What was done?

This is caused by ansible/ansible#76322
Added export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES if running on macOS

How Has This Been Tested?

On @shumkov's mac

Breaking Changes

None

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone