Use helpers for dealing with confusing "0"/"1" boolean values

This is an approach to fix #971. This adds `config_boolean_true?` and `config_boolean_false?` to wrap boolean field values. Due to the way services are currently stored in GitHub, these boolean config values will be passed as either "1", "0", or `nil`.

We've decided not to massage these into `true`/`false` values, since "1"/"0" is consistent with the hooks API responses.

**Note:** I'm not tied to these helper names but wanted to lean toward something pretty explicit. I'm definitely up for changing them if someone has any good ideas.

/cc @kdaigle
I sort of wish this didn't hide the `data` attribute. That's obviously way DRYer but in terms of explicitness for contributors I figured a helper that just compared whatever was passed in would be clearer. Thoughts?