Updates publish-to-s3 plugin to 0.7.0 for react-native-bridge & react-native-aztec Android and publishes '-sources.jar'

[oguzkocer]

Description

This PR updates publish-to-s3 Gradle plugin to 0.7.0 for react-native-bridge & react-native-aztec Android libraries and uses the newly introduced androidSourcesJar task to upload the -sources.jar file so it can be used by developers to access the source code from their IDEs. More details can be found in: Automattic/publish-to-s3-gradle-plugin#29

As of 0.7.0 version of the publish-to-s3 plugin, the publishToS3Plugin extension is no longer necessary, so as part of this update, the extension is removed from each project.

aztecVersion is also updated from v1.4.0 to v1.5.0 which brings the exact same changes to AztecEditor-Android: wordpress-mobile/AztecEditor-Android#942

Note that since there is no rush to get this changes in, there is no gutenberg-mobile PR for this PR.

How has this been tested?

The version upgrade for the plugin has been tested in wordpress-mobile/WordPress-Android#15492 and applied to several other libraries.

wordpress-mobile/gutenberg-mobile#4177 is used to verify the publishing still works as expected.

wordpress-mobile/WordPress-Android#15506 is used to test the aztecVersion change as well as to verify that the source files are available as part of this change.

Types of changes

Gradle plugin version change for react-native-bridge & react-native-aztec Android projects.

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• I've tested my changes with keyboard and screen readers.
• 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 (please manually search all *.native.js files for terms that need renaming or removal).

[oguzkocer]

@mchowning I missed something minor when I first opened the PR and pushed another commit to fix it. That made me feel a bit skeptical about not opening a PR for gb-mobile and possibly WPAndroid for testing. I'll do those and mark this as ready for review. Sorry about that!

[oguzkocer]

@mchowning I've ran the necessary tests, updated the PR description and marked the PR as ready for review again. Sorry for not covering everything from the start.

[mchowning]

Working great for me! Having the source available with the artifact is soo nice! Thanks @oguzkocer ! 🙇

As long as there are no changes to WPAndroid or gb-mobile that need to go along with this, the easiest thing would be to just merge this PR and not worry about those repos. These changes will get brought in the next time we incorporate the latest Gutenberg code (which happens multiple times every week). If there are related changes (I'm looking a bit suspiciously at the aztecVersion in WPAndroid, although I "feel" like that shouldn't actually cause any problems) we'll just need to make sure we merge to WPAndroid's after_#.## branch instead of develop.

[oguzkocer]

Thanks @mchowning! The aztecVersion update is the only thing that needs to change in WPAndroid, but it actually doesn't necessarily need to happen as soon as the gb-mobile update happens. I'll create the PR against the after_#.## branch for this change.