feat(requestinterception): don't disable cache by default

[Androbin]

Reverts #1154 @aslushnikov disabling the cache by default.

People don't expect this behavior, see tickets like: #2905, #3403. #4055, #4620, #5176, #6915, ...

There were two reasons for this change:

• Some sites did not fire the load event with caching enabled.
  • analysed in Request interception with caching (rev 8695759) fails when loading stylesheet-initiated fonts (?) #7038 @starrify
  • fixed in fix(requestinterception): fix font loading issue #7060
• We cannot intercept requests that are answered from the cache.
  • Most people are willing to accept cached resources not being intercepted.

This flag has been introduced in #6996.

[Androbin]

@OrKoN @jschfflr PTAL

[Androbin]

I personally prefer #7217

[jschfflr]

@Androbin Could you elaborate what you want to achieve here?

[Androbin]

There was bug that forced us to implicitly disable the cache when enabling interception.
This flag was added to allow people to override that behavior while keeping it the default behavior.
Now the bug in question is fixed and it is safe to change the default behavior.

[Androbin]

People expect interception and caching to be independent and that's how it was before #1154.

[jschfflr]

Closing this in favor of #7215