Jetpack: Replace HEREDOC syntax with strings

[bindlegirl]

Fixes https://github.com/Automattic/vulcan/issues/336

Proposed changes:

• Replaced HEREDOC syntax with multiline strings.

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

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

Testing instructions:

• Does it make sense?
• Does it break anything (logo or module syncing)?

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WordPress.com Simple site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin, and enable the update/heredoc-replacements branch.

  • For jetpack-mu-wpcom changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack update/heredoc-replacements
  

  bin/jetpack-downloader test jetpack-mu-wpcom-plugin update/heredoc-replacements
  

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[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.
  
• ✅ 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 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 reviewed, it can then be merged.
If you need an extra review from someone familiar with the codebase, you can update the labels from "[Status] Needs Team Review" to "[Status] Needs Review", and in that case Jetpack Approvers will do a final review of your PR.

[coder-karen]

I both checked the JP logo on a test site and changed modules then scheduled a checksum and fix with the Jetpack debugger, and that had no issues, but I'm not so familiar with sync so perhaps there is a better way to do that?

Also, you should be able to remove the disabled sniff PEAR.Functions.FunctionCallSignature.Indent just by indenting the SQL in those two blocks by three tabs :) (unless of course that affects functionality somehow, I can't see how it would from similar searches)

[fgiannar]

I both checked the JP logo on a test site and changed modules then scheduled a checksum and fix with the Jetpack debugger, and that had no issues, but I'm not so familiar with sync so perhaps there is a better way to do that?

The changes are related with the Full Sync behaviour, so we can test this when the PR is ready for another review by triggering a Full Sync of all modules via the JB Debugger's Full Sync section :)

[bindlegirl]

Thanks for checking it out @coder-karen ! I indented the SQL code as you suggested and tested the Full Sync as @fgiannar suggested.

[fgiannar]

LGTM 🚢