Move abiFilters caution callout on 'Integrate a Flutter module into your Android project' page

[neiljaywarner]

Page URL

https://docs.flutter.dev/add-to-app/android/project-setup

Page source

https://github.com/flutter/website/tree/main/src/development/add-to-app/android/project-setup.md

Describe the problem

abiFilters yellow box is advanced, possibly edge case, possible confusing.

I'm concerned it will make this page significantly less approachable (combined with the invalid screenshot below concerning an outdated IDE feature) to people new to Flutter, Android and/or add2app.

Expected fix

1. Move this warning to the bottom or another section or both. If nothing else make it expandable div and collapsed by default.
2. add a little more context/explanation about how to evaluate the disadvantagers of limiting supported architectures, it may make people nervous
3. in particular if 99.7 or so percentage of devices don't need this then that would be good to note.
4. Even a link explaining if/when/why emulators might sometimes not support it would be great. (eg ci/cd situations where qt/hardware acceleration cannot be installed/supported etc)

Additional context

https://proandroiddev.com/reducing-apk-size-by-using-abi-filters-and-apk-split-74a68a885f4e https://yourdeets.medium.com/google-details-upcoming-64-bit-requirement-for-android-apps-on-the-play-store-2d45ec2f2af2 https://developer.android.com/ndk/guides/abis https://developer.android.com/studio/build/configure-apk-splits.html#mips_mips64_and_armeabi https://stackoverflow.com/questions/46453457/which-android-abis-cpu-architectures-do-i-need-to-serve. - this one in particular

Trying to find out how to evaulate this is pretty confusing and difficult. I did it 4 years ago and came to some mostly reasonable conclusions and couldn't really find/remember