Filter Options Don't Invalidate the Cache

[deckar01]

In #489 I spent a lot of time debugging why babel wouldn't work only to find out that the first run didn't have the presets option, but after it was added the original output remained in the cache.

Step to reproduce:

1. Add a filter to a bundle
2. Build the bundled asset
3. Change an option for the filter
4. Build the bundled asset

What happened:

The build after the option was changed still fetched the asset from the cache even though the filter might output different content.

What should have happened:

Modifying the filter option should have invalidated the cache on the next build.

Suggested fixes:

Incorporate the filter options into the cache's hash.

[deckar01]

This issue seems to persist even after disabling the cache and the manifest.

environment.assets_environment.cache = False
environment.assets_environment.manifest = False