Update translations with translator comment to a single line

[renatho]

Changes proposed in this Pull Request

• It updates all i18n functions to be in a single line when it contains a translator comment.
  • The reason is that the recommended way (that works with all tools that extracts the translations), is to add the translator comments immediately before the string with the placeholders, but the PHPCS and eslint rules for that requires it to be before the function, which makes it inconsistent when we have a multiline i18n function. More details about the PHPCS rule issue: Fixes I18NSniff for multi-line gettext calls WordPress/WordPress-Coding-Standards#1962
• It was also suggested to not use the _x (translation with context), and replace the HTML entities with the real char. But I decided to not do that, for now, to not have other implications, like invalidating the existing translations.

Testing instructions

• Go to Settings > General.
• Update the language of the site to a different language, like "Español".
• Go to Dashboard > Updates, and click on the button to update the translations.
• Go to Plugins, and click on Settings under SyntaxHighlighter plugin.
• Make sure the page continues working properly with the translations. Only the text "The language syntax to highlight with. You can .." doesn't have a translation for "Español".

Context

pxLjZ-79a-p2

[fjorgemota]

Looks good and works well! 🎉