Description

This PR is updating the gradle-node-plugin used in the react-native-bridge package to use a more actively maintained fork of the plugin. This is necessary to support building with Gradle 6.x, which WPAndroid wants to start using.

Related PRs

wordpress-mobile/gutenberg-mobile#2607
wordpress-mobile/WordPress-Android#12923

How has this been tested?

1. From WPAndroid check out Gutenberg-Mobile: Update gradle-node-plugin to use actively maintained fork wordpress-mobile/WordPress-Android#12923 and update the submodules (which will check out this branch in libs/gutenberg-mobile/gutenberg/)
2. Insure that you are not building gutenberg-mobile from source (i.e. the root gradle.properties file does not set wp.BUILD_GUTENBERG_FROM_SOURCE to be true).
3. Perform various builds (i.e., WasabiDebug, and VanillaRelease) and ensure there are no issues (at a minimum, that the gutenberg editor can be successfully started). Note that I found that the gutenberg editor would crash when loading if I did a VanillaDebug or JalapenoDebug build, but I had those same issues without the changes in this PR, so I think the changes in this PR are fine (I haven't had time to track down the cause of this problem yet).
4. Verify that the gutenberg editor works in the Installable Build generated for the WPAndroid PR.

Types of changes

Update build tooling for Android build of react-native-bridge package

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR.