docker: Add script to create "fake" translations for testing i18n

[anomiex]

Changes proposed in this Pull Request:

This adds a script, intended to be run inside the Jetpack Docker
environment, to create plugin translations for two fake languages.

• en_piglatin: All messages are translated into Pig Latin.
• en_rtl: All messages will display backwards, and the interface will be
  right-to-left.

Once you have run the script, in WordPress Admin > Settings > General
you should see the above two languages as options for "Site Language".

Note WordPress itself is not translated as described, the translations
are only created for messages in the specified plugin.

Jetpack product discussion

p1634159370450900-slack-CBG1CP4EN

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

No

Testing instructions:

• Make sure you have the latest docker image, last I checked the one from Docker was outdated. You might need to jetpack docker build-image.
• Run jetpack docker exec /var/scripts/fakepot.sh /var/www/html/wp-content/plugins/jetpack
• Open your site to /wp-admin/options-general.php. You should see the two new languages in the Site Languages dropdown.
• If you select "en_piglatin" and go to the Jetpack dashboard, you should see something like this:
  
• If you select "en_rtl" and go to the Jetpack dashboard, you should see something like this:
  

[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.

[jeherve]

That should be useful, thank you.

I wonder if we should make this an option in the Jetpack Debug helper plugin UI right away?

[anomiex]

Unless the Jetpack Debug Helper is already monorepo-only, it would need some work:

• Remove the use of stuff from the monorepo tools/includes/ that may not be available.
• Detect whether Jetpack is the monorepo copy where we need to make a pseudo-built version, or an already-built version installed in some other way (e.g. Jetpack Beta) where we don't need to and probably can't because it's not a git repo.
• Don't just assume WordPress is at /var/www/html/.
• Will the calls to wp make-pot and such always work as written?
• Will the node cli command always be available?
• Will pnpm always be available for line 99? Could switching to npm there help?

[sdixon194]

Tested this out, but even after cleaning docker, building image, and upping again, I'm getting:

Success: Created 4 files.
Copying translations into /var/www/html/wp-content/languages/plugins/
cp: target '/var/www/html/wp-content/languages/plugins/' is not a directory
Cleaning up /tmp/fakepot.06MTtKk
Command exited with status 1

What am I missing here 🤔

[anomiex]

You hadn't installed any language packs before, so the directory for the plugin language packs didn't exist. Updated the script to create the directory.