PWA-1734: Configure staging and production responses to be gzipped

[anthoula]

Description

Compress HTML responses with gzip

Related Issue

Closes PWA-1734.

Acceptance

HTML is gzipped for staging and production

Verification Stakeholders

Specification

Verification Steps

Test Plan

Test scenario(s) for direct fix/feature

• Verify that the network request for your HTML file (ex: 'venia.magento.com') has a Response Header called "content-encoding" whose value is set to "gzip".

Test scenario(s) for any existing impacted features/areas

• n/a

Test scenario(s) for any Magento Backend Supported Configurations

• n/a

Is Browser/Device testing needed?

• No, just verify correct compression is used in the developer tools

Any ad-hoc/edge case scenarios that need to be considered?

• No

Screenshots / Screen Captures (if appropriate)

Breaking Changes (if any)

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]

	Messages
📖	Associated JIRA tickets: PWA-1734.
📖	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.

Generated by 🚫 dangerJS against 1e39b08

[revanth0212]

Code looks straightforward but how can I verify this?

[revanth0212]

Working 👏

[larsroettig]

✔️ QA aprrove