Added script to automate cloudflare cache purge

[kurtisassad]

Link to Issue

Closes: #8487

Test Plan

• (Locally) With the required env vars in your .env file, run the script with tsx ./purgeCloudflareCache.ts, you should get a success response from the cloudflare api indicating that the cache has been purged.
• On frick make a release and check to make sure that the script has run.

Deployment Plan

Need to add env vars CF_ZONE_ID and CF_API_KEY to heroku.

[rbennettcw]

looks fine though I think the errors should propagate to a single point and result in a non-zero exit code because the runtime environment usually does utilize that info somehow

[timolegros]

Couple more comments. Does this release phase step work conceptually (I might be missing something)? The dynos will not have restarted yet when the release phase is running so they will still be serving the old code, won't the cache repopulate with the existing app files instead of repopulating with the new app files that are deployed after the script completes? Seems like cache clearing needs to happen after deployment not during release no?

resolved comments