Internal server error if published defaultTopicTrigger references a draft topic

[aaronschachter]

BUG

Current Behavior

• A few endpoints (e.g. GET defaultTopicTriggers, GET /topics, GET /campaigns) return 500 errors in production if a published defaultTopicTrigger has a response reference to a draft topic. The error message returned is Cannot read property 'sys' of undefined. Slack thread

Desired Behavior

• Probably the best course of action would be for the offending entry to no longer loaded as a default topic trigger in production, but we should be alerted that there's been a misconfiguration.

Steps to Replicate

• This can be replicated by following these steps every time, but unfortunately would cause a similar production meltdown since we use the same Contentful environment for testing and production.

Why This Matters

Causes system breakage, and is relatively easy to do if not paying attention in the Contentful UI