* PoC: Add the changes requested status

* Add a new hided button for the new status

* Add a new listener for the new status button

* Add the new status (changes_requested) in the bulk post and bulk approve

* Update a failing test

* Update the package-lock.json with "npm update"

* Update the package-lock.json with "npm update"

* Update the package-lock.json from #1452

* Add the minimized JavaScript

* Add some checks to view the new status only with the WPORG_TRANSLATE_BLOGID constant available

To view the new status in the frontend, you need to add the WPORG_TRANSLATE_BLOGID
constant in the wp-config.php file with the value of the get_current_blog_id() function. E.g.:

   define( 'WPORG_TRANSLATE_BLOGID', 1 );

* Update the check to see if the gp-translation-helpers plugin is installed

Check if the 'gp_translation_helper_installed' filter returns true -> plugin installed.

* Update the filter name from gp_translation_helper_installed to gp_enable_changes_requested_status

* Some updates to show the changes_requested strings as rejected if the gp_enable_changes_requested_status is not enabled

* Set the changes_requested as untranslated if the gp_enable_changes_requested_status is not enabled

* Update the margin for the action buttons

* Update the hook for the changes_requested buttons

* Update texts: changes_requested to changesrequested and request_changes to requestchanges

* Resolve a bug in the filter form

* Update the changesrequested showed value, with the uppercase

* Bugfix. Update the value for the changesrequested value if this status is not enabled

* Rearrange some conditions in an if statement

* Add some comments in an if and remove some parenthesis

* Add some comments in an if and remove some parenthesis

* Add a stub for set_status_changesrequested, avoiding breaking the plugin when the gp-translation-helpers plugin is not installed.

Props @akirk #1451 (review)