Double check what would happen if we are rate limited by WP on Circle CI

[willdurand]

This should fail the deployment process ideally and not remove the existing content...

┆Issue is synchronized with this Jira Task

[willdurand]

I am wondering how to simulate this. The build fails when it is unable to receive correct JSON (e.g., by pointing to a non-existent WP instance) but it isn't quite the same as a rate limit error, which should be a 429 or something.

An idea I had was to add some simple tests ran after we build the blog on Circle CI, see: #255. It isn't going to fully fix this issue but that should avoid a catastrophic scenario.