2.1.0

• Individual rules in the cache_control can now again have a match_response
  or additional_response_status configuration to limit the rule to certain
  responses.

  For this, the signature of CacheControlListener::addRule had to be changed.
  It now expects a RuleMatcherInterface instead of the
  ResponseMatcherInterface. If you extended the listener or change the service
  configuration, this could be a BC BREAK for your application.

• If no response matching is configured on cache_control, the global
  cacheable configuration is now respected to decide whether cache headers
  should be set.