When viewing an a content object containing a `ezlandingpage` field type, each block is supposed to be rendered using a separate ESI.

However, I noticed that if hitting ctrl+F5 on such page ( and the page is not already in the http cache), the page will be rendered without ESIs. Instead, content of each block is rendered inline (subrequests).
When using ctrl+F5, the browser ( at least FireFox) adds a Pragma: no-cache header in the request.

In PageBuilder, there is an error causing all blocks to be rendered inline instead of as esi if clients requests a non-cached version of the resource

The check $request->isNoCache() should be removed ! Clients should not be able to decide if we are going use ESIs or not.

Once the request has been rendered inline, that version will be stored in the HTTP-CACHE and served to other clients