Include strings referenced in GB-mobile files in localization strings files

[fluiddot]

In the file strings-overrides.js (reference) we have some strings which are not currently translated due to not being included in the localization strings files. This PR adds new make-pot commands to extract strings also from source files of GB-mobile repository.

Strings referenced in GB-mobile:

• gutenberg-mobile/src/strings-overrides.js

  Lines 19 to 21 in 313e993

  	const unsupportedBlocksExplanation = __(
  	'You can edit this block using the web version of the editor.'
  	);

• gutenberg-mobile/src/strings-overrides.js

  Lines 27 to 29 in 313e993

  	const note = __(
  	'Note: You must allow WordPress.com login to edit this block in the mobile editor.'
  	);

• gutenberg-mobile/src/strings-overrides.js

  Line 55 in 313e993

  ? __( 'Open Jetpack Security settings' )

These strings are mainly used in the unsupported block editor modal:

To test:

1. Run command npm run genstrings.
2. Observe that the localization strings files (bundle/ios/GutenbergNativeTranslations.swift and bundle/android/strings.xml) remain unmodified.
   NOTE: Most likely the string Text color would be added if Specify domain when extracting strings from Jetpack and Layout Grid #4409 is not already merged, please omit this string as it will be included on that PR.

PR submission checklist:

• I have considered adding unit tests where possible.
• I have considered if this change warrants user-facing release notes more info and have added them to RELEASE-NOTES.txt if necessary.

[peril-wordpress-mobile]

Wanna run full suite of Android and iOS UI tests? Click here and 'Approve' CI job!

[ttahmouch]

Hey, @fluiddot . We will cut the 1.69.0 release on Thursday, January 6, 2022. We plan to circle back and bump this PR to the next milestone then, but please let me know if you'd rather us work to include this PR in 1.69.0.

[jhnstn]

Looks good. npm run genstrings executed as expected.
(I did get the "Text color" string as you noted in the test steps.)