[Cookbook][Cache] Added config example for Varnish 4.0

| Q             | A
| ------------- | ---
| Doc fix?      | [yes]
| New docs?     | [no] 
| Applies to    | [all]
| Fixed tickets | []

After upgrading to `Varnish 4.0`, I've noticed the documentation was not really up-to-date anymore:

 * according to https://www.varnish-cache.org/docs/4.0/whats-new/upgrading.html#req-not-available-in-vcl-backend-response,
   
  `beresp` is available in `vcl_backend_response`

 * according to https://www.varnish-cache.org/docs/4.0/whats-new/upgrading.html#hit-for-pass-objects-are-created-using-beresp-uncacheable,

   `hit_for_pass` objects are created via `beresp.uncacheable`

Would this addition be enough in order to consider the documentation up-to-date in accordance with `Varnish 4.0` upgrading guidelines?
why X-No-Cache? i think the idea is to respect all no-cache variations to be sure we respect what symfony is telling us in the default headers.

afaik symfony does not set a X-No-Cache header by default. i would make the varnish 4 config the same as the varnish 3 config, only leave out the headers that are now uncacheable by default.