fontFamily "Courier" is not a system font and has not been loaded through Font.loadAsync. (When using <Code/> component)

### Description

happens in IOS simulator

### CodeSandbox/Snack link

react-native expo template

### Steps to reproduce

1. expo init my-app --template @native-base/expo-template
2. yarn ios

### NativeBase Version

3.3.7 and also latest alpha

### Platform

- [ ] Android
- [ ] CRA
- [ ] Expo
- [X] iOS
- [ ] Next

### Other Platform

_No response_

### Additional Information

fontFamily "Courier" is not a system font and has not been loaded through Font.loadAsync.

- If you intended to use a system font, make sure you typed the name correctly and that it is supported by your device operating system.

- If this is a custom font, be sure to load it with Font.loadAsync.
at node_modules/expo-font/build/Font.js:27:16 in processFontFamily
at node_modules/react-native/Libraries/ReactNative/renderApplication.js:54:4 in renderApplication
at node_modules/react-native/Libraries/ReactNative/AppRegistry.js:117:25 in runnables.appKey.run
at node_modules/react-native/Libraries/ReactNative/AppRegistry.js:213:4 in runApplication

Reproduce the warning with the NativeBase Expo template on the iOS simulator, then trace the reported path through node_modules/expo-font/build/Font.js and React Native's renderApplication.js. Confirm that the component is the trigger and that the completed change removes the warning without breaking the example.

Written by the indexing model from the issue text.