BUG: Translation of JavaScript files

[felipeelia]

Describe the bug

Although we are using WordPress i18n functions in JS files, currently it is not possible to translate any of those strings.

Here is the list of things that needs to be changed:

• 1. For each wp_enqueue_script() or wp_register_script() call we have, a call to wp_set_script_translations() needs to be added;
• 2. We need to check if blocks' JS files also need that function call;
• 2. The command responsible for parsing JS files and their i18n function calls ignores min files. To have them parsed, we will need to rename the min.js files to simply .js;
• 3. To help people that are translating the plugin outside of the WP.org environment, we probably could add a make-pot call during the release process.

Some additional context:

• The repo used by WP.org to parse plugins (not necessarily the exact line)
• Example of string pointing to the original JS file and not the minified version
• Example of WooCommerce string pointing to the minified file. Note the lack of .min.js in the file extension
• Example of a Yoast string pointing to several minified files
• Our .pot file is NOT taken into account by WP.org. It is severely outdated but WP.org has captured all strings (including the JS ones) in the origin files.