Add an optional significant_version to the cache busting

[winhamwr]

If a task's output format changes, the previous result might still be cached, even though the result should now be different even for the same significant_kwargs.

If at a task has a significant_version property, include that in the cache key. That will allow developers to bump that number any time they need to invalidate old results because of a change in the task itself.