[expo] Disable autolinking if project do not have expo modules installed

[Kudo]

Why

to make expo-cli works fine for bare react-native projects without setup expo-modules correctly.
there were errors like this when pod install

[!] Unable to find a specification for `ExpoModulesCore` depended upon by `Expo`

You have either:
 * out-of-date source repos which you can update with `pod repo update` or with `pod install --repo-update`.
 * mistyped the name or version.
 * not added the source repo that hosts the Podspec to your Podfile.

close ENG-8606

How

enable rn-cli autolinking only if it passes the simple check for Podfile and settings.gradle

Test Plan

• ci passed
• tested on npx react-native@latest init RN071 --version 0.71 project + expo package with this patch
• tested on npx react-native@latest init RN071 --version 0.71 project + install-expo-modules with this patch
• tested on yarn create expo -t blank@sdk-48 sdk48 with this patch

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-8606 Investigate feasibility of changing how `expo` is linked

Can we make it so it doesn't need to be linked by react-native-community/autolinking, if we add one additional setup step when installing the package to link it manually? (install-expo-modules could do this for most people)

[Kudo]

@brentvatne this pr tries to solve ENG-8606 from an easier sanity check. please review if the solution makes sense to you.

[brentvatne]

clever solution! nice on @Kudo