fix pom file not found when run app with local engine

[zsunkun]

Description

When I run app with local engine,I get the following error:

Launching lib/main.dart on MI 6X in debug mode...
The file /Users/xxx/engine/src/out/android_debug/arm64_v8a_debug.pom wasn't found in the local engine out directory.

This is the content of my android_debug directory，it only has armeabi_v7a_debug.pom:

After fixed it, I got another problem:

* What went wrong:                                                      
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.
> Could not resolve all task dependencies for configuration ':app:debugCompileClasspath'.
   > Could not find any matches for io.flutter:arm64_v8a_debug:+ as no versions of io.flutter:arm64_v8a_debug are available.
     Required by:                                                       
         project :app 

The reason for both issues is that getting the pom name and target-platform are both dependent on my phone(arm64). I think when using a local Engine, it should depend on the engine out path

flutter dcotor:

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel v1.12.13-hotfixes, v1.12.13+hotfix.8, on Mac OS X 10.14.6 18G103, locale zh-Hans-CN)
[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    ✗ Android license status unknown.
      Try re-installing or updating your Android SDK Manager.
      See https://developer.android.com/studio/#downloads or visit https://flutter.dev/setup/#android-setup for detailed instructions.
[✓] Xcode - develop for iOS and macOS (Xcode 11.3)
[✓] Android Studio (version 3.5)
[✓] Connected device (1 available)

Related Issues

Tests

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

• I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
• I signed the [CLA].
• I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
• I read the [Tree Hygiene] wiki page, which explains my responsibilities.
• I updated/added relevant documentation (doc comments with ///).
• All existing and new tests are passing.
• The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Did any tests fail when you ran them? Please read [Handling breaking changes].

• No, no existing tests failed, so this is not a breaking change.

Fixes #48276

[fluttergithubbot]

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie.

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

[jonahwilliams]

FYI @xster @blasten

[blasten]

Thanks @zsunkun. This LG, but what about adding some unit tests in gradle_test.dart?

[jmagman]

build_apk_test test failures need to be addressed as well as new tests added.
https://cirrus-ci.com/task/4736705525710848?command=main#L818

[zsunkun]

build_apk_test test failures need to be addressed as well as new tests added.
https://cirrus-ci.com/task/4736705525710848?command=main#L818

@jmagman @blasten Unit tests have been updated

[blasten]

It might be worth testing each platform as well.

[blasten]

LGTM