Feature/wpcli i18n tooling

[carstingaxion]

As a translation contributor it is super-handy to use the i18n-tooling, that is included in wp-cli by default. So I would suggest adding it, at least to the development-requirements for GatherPress.

But ... how to install wp-cli is heavily different depending on the system, you want to run it on. This is well documented at Installing – WP-CLI – WordPress.org. That's why we can not or should not just add it it to GatherPress' composer dependencies.

Description of the Change

This PR only suggests the wp-cli package via composer.josn, but leaves the decision open on how and where to install it.

Assuming wp-cli is installed now per the suggestion within the dev environment, someone can now use three new scripts to create translation files for GatherPress.

npm run i18n:pot
npm run i18n:json
npm run i18n:php

The third script provides access to the new performant translations functionality, introduced in WP 6.5 and already mentioned by @patriciabt over here.

Closes #

How to test the Change

...

Changelog Entry

Added - i18n tooling by wp-cli

Credits

Props @carstingaxion

Checklist:

• I agree to follow this project's Code of Conduct.
• I have updated the documentation accordingly.
• I have added tests to cover my change.
• All new and existing tests pass.

[carstingaxion]

Seems, we need to exclude the newly generated performant translation files from the CS checks.

[mauteri]

Seems, we need to exclude the newly generated performant translation files from the CS checks.

Just committed change for that for you.

[carstingaxion]

Incredible, how fast you were @mauteri. Thanks!