Repository: godot
Issue: exporting android build fails with checkDebugAarMetadata / checkReleaseAarMetadata
Labels: bug,platform:android,topic:plugin,topic:thirdparty,needs testing,topic:export

### Godot version

3.3.4.stable, 3.4.0.stable, 3.4.1.stable

### System information

MacOS 11.3 Big Sur, MacOS 11.6 Big Sur

### Issue description

We started to get the following issue when trying to export/make android build with more than one android plugin enabled:

```
Starting a Gradle Daemon (subsequent builds will be faster)
> Task :clean
> Task :assetPacks:installTime:clean UP-TO-DATE
> Task :preBuild UP-TO-DATE
> Task :preDebugBuild UP-TO-DATE
> Task :compileDebugAidl NO-SOURCE
> Task :compileDebugRenderscript NO-SOURCE
> Task :generateDebugBuildConfig
> Task :javaPreCompileDebug
> Task :checkDebugAarMetadata FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':checkDebugAarMetadata'.
> Could not resolve all files for configuration ':debugRuntimeClasspath'.
   > Could not resolve com.gameanalytics.sdk:gameanalytics-android:6.1.1.
     Required by:
         project :
      > Could not resolve com.gameanalytics.sdk:gameanalytics-android:6.1.1.
         > Could not get resource 'https://dl.bintray.com/mobilap/maven/com/gameanalytics/sdk/gameanalytics-android/6.1.1/gameanalytics-android-6.1.1.pom'.
            > Could not HEAD 'https://dl.bintray.com/mobilap/maven/com/gameanalytics/sdk/gameanalytics-android/6.1.1/gameanalytics-android-6.1.1.pom'. Received status code 502 from server: Bad Gateway

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 15s
5 actionable tasks: 4 executed, 1 up-to-date

Exit Code: 1
```

We *started* to have this issue with Godot `3.3.4.stable` after a break in activity, without making changes to the source code or updating operating system components. We made the last successful build end of October, then when trying to make a new build in the beginning of December, it started to fail with this error. It happened on a couple of separate machines. Given that Godot AssetLib also stopped working, we upgraded to the new Godot versions but it didn't help.

We have 3 gdap files in the `android/plugins` folder: *AppLovinMax.gdap, GameAnalytics.gdap, LocalNotification.gdap*. What we noticed was that the `[dependencies]/remote` and `[dependencies]/custom_maven_repos` components get mixed up? I.e. having Game Analytics and Local Notifications plugins enabled with the following contents
*GameAnalytics.gdap*
```
...
[dependencies]
remote=["com.gameanalytics.sdk:gameanalytics-android:6.1.1"]
custom_maven_repos=["https://maven.gameanalytics.com/release"]
```
*LocalNotification.gdap*
```
[dependencies]
local=[]
remote=[]
custom_maven_repos=["https://dl.bintray.com/mobilap/maven/"]
```

Then the error above looks like it tries to pull the gameanalytics `com.gameanalytics.sdk:gameanalytics-android:6.1.1` dependency from the LocalNotifications `custom_maven_repos=["https://dl.bintray.com/mobilap/maven/"]` repo?

If we keep only one Android plugin enabled in the export settings, then all works.



### Steps to reproduce

Export Android build with more than one plugin enabled.


### Minimal reproduction project

_No response_