Lock cookiejar at 0.3.0

[ajb]

Per this issue: dwaite/cookiejar#13 (comment)

This probably should be considered urgent.

[jcoglan]

I don't think this should be done in packages that depend on cookiejar, because gems with too-strict versioned dependencies are likely to conflict with one another, rendering it impossible to use two packages that depend on different versions of cookiejar in the same project.

Because Ruby has a single dependency namespace, and you cannot run two versions of a gem in the same process, I think it needs to be left up to the end user to specify gem 'cookiejar', '0.3.0' if they are having problems. This seems like a temporary problem anyway that should be fixed with another release of cookiejar, and it seems wrong for all downstream gems to lock their dependencies in the interim.

[ajb]

Unfortunately, it seems that the maintainer of cookiejar is MIA at present, but agreed that fixing cookiejar is obviously a better solution.

[ajb]

And naturally, cookiejar 0.3.2 is released as soon as I open this PR. Sorry to bother :)