PWA-2355 UPWARD JS resolver for Computed type

[justinconabree]

Description

To bring the JS implementation of the UPWARD spec closer to the PHP implementation, we've added the Computed resolver to it as well. The resolver simply returns an empty string so the application can continue without error.

Related Issue

Closes PWA-2355

Acceptance

Verification Stakeholders

@zetlen

Specification

Changes to upward-spec and/or upward-js packages must be reviewed

Verification Steps

Test scenario(s) for direct fix/feature

• Run DEBUG=upward-js:ComputedResolver yarn stage:venia
• Visit front-end
• Should see upward-js:ComputedResolver Computed resolver is meant for UPWARD PHP only in the terminal
• Site should function normally, and inlined data should be missing from source (see screenshot for reference)
  

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

• Test using UPWARD PHP
• Inlined data should be available (Can look for global variable INLINED_PAGE_TYPE in browser console)

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.

[pwa-studio-bot]

	Fails
🚫	A version label is required. A maintainer must add one.

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

[mikhaelbois]

LGTM ✅

[fooman]

Wouldn't we be able to at least supply webpageChunks based on the page type similar to how the php implementation globs for those files?

[justinconabree]

@fooman Not without the page type information unfortunately. Each root component is its own chunk (sometimes more than one), and we only inline the chunks for the current page type.