Blaze: do not require JSON API module anymore.

[jeherve]

Proposed changes:

This effectively reverts #28267. This check should no longer be necessary when D97667-code will be committed.

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

• 1386-gh-dotcom-forge

Does this pull request change what data or activity we track or use?

• No

Testing instructions:

Note
You will not be able to test this until the above diff is committed.

• Test on a public WoA site
• Go to the Post list, in wp-admin: wp-admin/edit.php?post_type=post
• You should see the "Blaze" option when moving your mouse over a post row (if the post is published).
• Go to https://yoursite.com/wp-admin/admin.php?page=jetpack_modules
• Disable the JSON API module.
• Reload the post list in wp-admin.
• The Blaze option should still be there.
• Click on one of the links.
• Ensure the Calypso page loads fully.

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ All commits were linted before commit.
  
• ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Once your PR is ready for review, check one last time that all required checks (other than "Required review") appearing at the bottom of this PR are passing or skipped.
Then, add the "[Status] Needs Team review" label and ask someone from your team review the code.
Once you’ve done so, switch to the "[Status] Needs Review" label; someone from Jetpack Crew will then review this PR and merge it to be included in the next Jetpack release.

[github-actions]

Are you an Automattician? You can now test your Pull Request on WordPress.com. On your sandbox, run

bin/jetpack-downloader test jetpack rm/blaze-json-api-gate

to get started. More details: p9dueE-5Nn-p2

[zinigor]

Since the diff was merged, this should be good to go.

[samiff]

cherry-picked to jetpack/branch-11.8 in new package version automattic/jetpack-blaze v0.5.1