If a change was made to a review request with a pluggable field, and
that field was no longer available (due to the extension no longer being
enabled), the code would fail, resulting in an HTTP 500.

We now check to make sure the field is there before including the
serialized contents in the payload.

I was hitting this problem locally. This fixed it.