#3114 Set fetch policy and next fetch policy for cms block query

[vasilii-b]

Description

This PR sets the fetch policy for CMS Block.

Related Issue

Closes #3114.

Acceptance

N/A

Verification Stakeholders

Specification

Screenshots / Screen Captures (if appropriate)

N/A

Checklist

• I have added tests to cover my changes, if necessary.
• I have added translations for new strings, if necessary.
• I have updated the documentation accordingly, if necessary.

[PWAStudioBot]

	Fails
🚫	A version label is required. A maintainer must add one.
🚫	Missing "Verification Steps" section. Please add it back, with detail.

	Messages
📖	DangerCI Failures related to missing labels/description/linked issues/etc will persist until the next push or next nightly build run (assuming they are fixed).
📖	Access a deployed version of this PR here. Make sure to wait for the "pwa-pull-request-deploy" job to complete.

If your PR is missing information, check against the original template here. At a minimum you must have the section headers from the template and provide some information in each section.

Generated by 🚫 dangerJS against f86391e

[fooman]

wouldn't cache-first mean that updated content would not show if it was edited again?
https://medium.com/@galen.corey/understanding-apollo-fetch-policies-705b5ad71980?

[sirugh]

wouldn't cache-first mean that updated content would not show if it was edited again?

On first load, cache-and-network always updates with network (server) data. But if that data ever changes on the client, the query makes another call to the server. We applied the nextFetchPolicy to avoid excessive server calls as it allows the initial network fetch but then always trusts the cache from then on (for this page load).

[dpatil-magento]

QA Approved.