Move parsoid-specific code out of the pagecontent bucket handler

For ease of review, I tried to keep each commit atomic (and non-breaking) so that the progress of the refactor is captured.

There's still some cleanup needed, but all the code migration should be done.

This will somewhat deprecate #46, since it will be used to support the cache-control header for parsoid-generated data.  This PR does not address the general pattern of cache-control header support on all endpoints.
Hmm, yeah.. The current tests are using some random bucket name to avoid clobbering actual production data. Maybe we could use a standard bucket name, but a random domain instead?