Spike - Continue Zap Sleep Investigation

[elipe17]

Description: This is a follow on task to finish the investigation from #2946 into why we need to insert a 4 minute sleep to ensure the nightly owasp scan successfully executes and uploads it's results to the DAC.

Acceptance Criteria: Create a list of functional outcomes that must be achieved to complete this issue

• [ ] Ideally the removal of the sleep from the pipeline
• [ ] If the sleep can't be removed, document any further findings as to why the sleep is necessary and what issue/issues it is "fixing".
• [ ] Testing Checklist has been run and all tests pass
• [ ] README is updated, if necessary

Tasks: Create a list of granular, specific work items that must be completed to deliver the desired outcomes of this issue

• [ ] Continue investigation based on results and further tests outlined in: zap_trials.md
• [ ] Run Testing Checklist and confirm all tests pass

Notes: Add additional useful information, such as related issues and functionality that isn't covered by this specific issue, and other considerations that will be helpful for anyone reading this

Supporting Documentation: Please include any relevant log snippets/files/screen shots

Open Questions: Please include any questions or decisions that must be made before beginning work or to confidently call this issue complete

[robgendron]

A few more hours needed, aiming for EOW.

[raftmsohani]

The "cf" command is responding with 202 instead of 200, which means cloud.gov is receiving the request but not running it:

What I see when running the command in my local env:

What we see in circleci: