httplib2 0.12.0 release breaks cert handling

[JNRowe]

Upstream has massively changed the way they handle certificates, and we’ll need to adapt to make that work.

It isn’t clear if we should be forcing <0.12.0, or attempt to produce a workaround that works with both. It will depend on the complexity.

[Note to self: Ping Matt for his 2c on the chances of getting 0.12.0 promoted up the queue for packaging. Without that forcing <0.12.0 is probably the only option.]

[JNRowe]

I've pushed this with forced <0.12, as it is breaking deployments. It really isn't clear what the correct way to move forward is, 0.12 isn't going to be packaged globally anytime soon and increased complexity to cover both is huge.

Matt has at least pushed in a really cool QA check to make sure nobody is accidentally receiving the incorrect certificates, but obviously that isn't going to work for people who aren't using our infrastructure.

Weekend to spin...

[JNRowe]

After [once again] talking this over with co-workers the decision to stop supporting httplib2 in other projects has been made. So jnrbase.httplib2_certs will be deprecated in 1.2, and gone in 1.3.