feat(clerk-expo): Remove headers causing CORS errors

[thiskevinwang]

Description

This removes two headers, added in #2528, that are resulting in CORS errors being returned from the Clerk Frontend API.

Related:

• feat(clerk-expo): Add expo data to request headers #2528 (comment)
• getToken method returns null right after isSIgnedIn becomes true #2266

Checklist

• npm test runs as expected.
• npm run build runs as expected.
• (If applicable) JSDoc comments have been added or updated for any package exports
• (If applicable) Documentation has been updated

Type of change

• 🐛 Bug fix
• 🌟 New feature
• 🔨 Breaking change
• 📖 Refactoring / dependency upgrade / documentation
• other:

[changeset-bot]

🦋 Changeset detected

Latest commit: 9e6b63f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@clerk/clerk-expo	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[panteliselef]

@thiskevinwang If having this kind of information was useful, and don't wanna completely removed it, couldn't we just do this ?

if(!isValidBrowser()) {
      // Send some non-identifying headers that are useful for logging
      (requestInit.headers as Headers).set('x-expo-execution-environment', Constants.executionEnvironment);
      (requestInit.headers as Headers).set(
        'x-expo-native-application-version',
        Application.nativeApplicationVersion || 'NULL',
      );
}

of use import { Platform } from 'react-native';

if (Platform.OS !== 'web') {
      // Send some non-identifying headers that are useful for logging
      (requestInit.headers as Headers).set('x-expo-execution-environment', Constants.executionEnvironment);
      (requestInit.headers as Headers).set(
        'x-expo-native-application-version',
        Application.nativeApplicationVersion || 'NULL',
      );
}

[thiskevinwang]

@panteliselef Oh, smart thinking! But also...

If having this kind of information was useful

...Turns out, it was not particularly useful so I'd say we just remove this!

[panteliselef]

lgtm

[anagstef]

@thiskevinwang Maybe we could make this a little bit easier to read, as it'll be included in the changelog which is facing the developers using our product. For example, let's mention what are the headers this change removes. :)

[thiskevinwang]

Updated in 05e82b4

[dimkl]

@thiskevinwang You should also remove those dependencies from the devDependencies.

[thiskevinwang]

Done in 05e82b4