[cli] Fix permission issue when user doesn't have permission to view app

[wschurman]

Why

When #21989 was written, it forgot to account for cases where the app isn't visible to the viewer (happens when app privacy is set to private). It had incorrectly assumed that all app privacy delegated to the viewer's permissions on the owning account.

Closes ENG-10719.

How

The fix is to treat errors thrown when trying to query an app as permission errors and return null for fetchAndCacheNewDevelopmentCodeSigningInfoAsync. Note that this does mask network errors, I think this is ignored when offline anyways.

Test Plan

Run new tests.

Manual test plan:

1. Log in to account that doesn't have permission on NCL
2. Build Expo Go locally
3. Build CLI locally
4. nexpo start
5. Load NCL before change, see error about Account entity not being visible.
6. Load NCL after change, see it works and is unsigned.

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-10719 Look into CLI issue where person running app in Expo Go doesn't have permission on account

https://exponent-internal.slack.com/archives/C013ZK4SA12/p1700687201751489

[wschurman]

Ping. This is a release blocker.

[ide]

Approving to unblock the release but I think there is a chance we'll want to revisit this and make the error checking even more precise, specifically by checking the GraphQL error for a specific error code (and doing similar for CombinedErrors if there is just one underlying error and it's a GraphQL error that matches)

[wschurman]

Approving to unblock the release but I think there is a chance we'll want to revisit this and make the error checking even more precise, specifically by checking the GraphQL error for a specific error code (and doing similar for CombinedErrors if there is just one underlying error and it's a GraphQL error that matches)

I thought about it, but there isn't a callsite in this codebase that does it with Graphql errors (only ApiV2Error and only for OTP).