[updates] Fix app.manifest occasionally missing on android

[Kudo]

Why

there are some reported issues that the app.manifest is missing from output builds.
close ENG-2610

How

i cannot reliably reproduce the problem and the hypothesis is about building task sequence. the pr tries changing the task dependency to mergeReleaseResources which would be earlier than processReleaseResources. this is also aligned with react-native implementation.

Test Plan

updates e2e ci passed (based on #19730)

Checklist

• Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
• Conforms with the Documentation Writing Style Guide
• This diff will work correctly for expo prebuild & EAS Build (eg: updated a module plugin).

[linear]

ENG-2610 Investigate expo-updates manifest not getting embedded in Android app with a lot of assets

A user reported that their Android app built with EAS Build was crashing due to the app.manifest ending up missing from the final APK. I added some logging to our createManifest.js script and it looks like we do successfully write app.manifest (see line 463 and onwards in gradlew phase). So it is somewhere after writing the file to android/app/build/generated/assets/expo-updates/release/app.manifest where this falls apart - possibly related to the [intermediates](https://github.com/expo/expo/blob/fd06ac0fc2296b3441d1e48896fded19883d8a43/packages/expo-updates/scripts/create-manifest-android.gradle#L66-L71) directory (@eric pointed out he wasn't super confident in this approach so it may be worth digging into more).

Example repo: https://gitlab.epsteindidntcommitsuici.de/eguillaumin/catamaps/-/tree/0c153891cad36928726eb73c3fa40c6efeb08eb0

I wasn't able to reproduce this on my machine, only on EAS Build. So the repro steps are to clone the exact commit provided above and then run eas build -p android --profile preview and inspect the resulting APK (apktool d -s file.apk -o outdir) - notice that app.manifest is missing from assets.

Note: the user was able to resolve this issue by compressing png to webp, so it does seem related to the size of assets. You can also verify that excluding the source by replacing App.js with some basic "Hello, world!" example (thus preventing importing the assets) will resolve the issue.

[brentvatne]

@douglowder - what do you think about this? can we land it for sdk 47? we've seen a handful of reports about this recently so it would be nice to land this if possible

[douglowder]

@brentvatne yes this seems safe to land.