Moving plugin release process to Bintray

[langsmith]

Resolves #915 by moving the plugin artifact release process to Bintray. The work in this pr is largely based off of similar work done in mapbox-gl-native and in the Java SDK.

[langsmith]

Right now on this pr, I get the following error when I run make publish after running build-release:

* What went wrong:
Execution failed for task ':plugin-annotation:publishMapboxPluginPublicationPublicationToMavenLocal'.
> Failed to publish publication 'MapboxPluginPublication' to repository 'mavenLocal'
   > Invalid publication 'MapboxPluginPublication': multiple artifacts with the identical extension and classifier ('aar', 'null').

I'm still looking into it. The fix might be making a separate MavenPublication for each plugin in the gradle-bintray.gradle file 😕 .

[langsmith]

So weird because there's only one .aar file per plugin after I do make build-release. I guess I'm misunderstanding something about a MavenPublication.

[langsmith]

This is on hold as we continue to explore alternative ways to deploy our products

[stale[bot]]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale[bot]]

This pull request has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions.

[stale[bot]]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale[bot]]

This pull request has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions.