[updates] fix fingerprint policy start error on debug build

[Kudo]

Why

fix android launch crash when a project using fingerprint runtime version policy with expo-updates and expo-dev-client
close ENG-12299

How

the crash is because on debug build we didn't generate the fingerprint file. this pr tries to generate fingerprint on debug build. this is aligned with our implementation on ios:

expo/packages/expo-updates/scripts/create-updates-resources-ios.sh

Lines 5 to 16 in 2cf0578

	CREATE_UPDATES_RESOURCES_MODE="all"
	if [[ "$SKIP_BUNDLING" ]]; then
	echo "SKIP_BUNDLING enabled; skipping create-manifest-ios.sh."
	CREATE_UPDATES_RESOURCES_MODE="only-fingerprint"
	elif [[ "$CONFIGURATION" == *Debug* ]]; then
	if [[ "$FORCE_BUNDLING" ]]; then
	echo "FORCE_BUNDLING enabled; continuing create-manifest-ios.sh."
	else
	CREATE_UPDATES_RESOURCES_MODE="only-fingerprint"
	fi
	fi

Test Plan

$ yarn create expo -t blank@sdk-51 sdk51
$ npx expo install expo-dev-client expo-updates
$ eas update:configure
# change runtimeVersion.policy to "fingerprint"
$ npx expo run:android

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 npx expo prebuild & EAS Build (eg: updated a module plugin).

[linear]

ENG-12299 User reporting updates crash on SDK 51 Android with runtimeVersion policy fingerprint (Android)

[expo-bot]

The Pull Request introduced fingerprint changes against the base commit: ec256db

Fingerprint diff

[
  {
    "type": "dir",
    "filePath": "../../packages/expo-updates/expo-updates-gradle-plugin",
    "reasons": [
      "expoAutolinkingAndroid"
    ],
    "hash": "5a34e34343ec9b806b643e2097bf6d6276fa24e2"
  }
]

---

Generated by PR labeler 🤖