We must fix pagination for plugin pages

Hey @parkr, I've created a branch with a failing test that demonstrates how pagination doesn't work with Octopress Ink plugins. I'd love your help figuring out how to address this major shortcoming. Without pagination Ink is very limited as a useful theming framework.

Here's the scoop. Pagination gets angry if the file isn't named "index.html" and if it doesn't appear in between source and the pagination dir. I honestly don't know why this is a restriction, but that's where my problems are coming from. With Ink plugins, the assets are stored in the gem, elsewhere on the filesystem and so it will never be acceptable as a pagination file.

To see this test fail, run `bundle exec clash 8` which will run the 8th (and final) test in the test suite. which simply builds Jekyll using the `_config_paginate.yml` and reading from to the `source_paginate` directory. The theme index file can be found at `test/_ink_plugins/blog-theme/pages/index.html` and you can monkey patch things in the `test/_ink_plugins/blog-theme/plugin.rb` file if you want to.

I'm happy to answer any questions you have about this feature and I'm happy to try things and push them if you like. Thanks for your help with this. :D
The more I think about it, a pagination template just seems unnecessary. What's wrong with making a liquid tag that uses it's parent file as a template and uses its *destination* directory as the configuration for where to write files? Right now most of the issue I'm having is related to the fact that this plugin cares about where the file came from instead of its destination.