[core] Removed all NativeModulesProxy occurrences

[reichhartd]

Why

In order to remove NativeModulesProxy from expo-modules-core in the future, I have replaced the use of it in all other packages.

How

I have replaced all occurrences of the deprecated NativeModulesProxy.

I have left the export of NativeModulesProxy in the index.ts of expo-modules-core, but can remove it if it is not too early.

Test Plan

Test cases run.

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).

[tsapeta]

Great, thank you so much! 🙏 I left some changelog suggestions, but in general it looks good.
Recently I had some troubles to move off of NativeModulesProxy in expo-font tests, but looks like they are passing now – which is great 👍

[reichhartd]

You're welcome 🙏
Is it too early to remove the export of NativeModulesProxy in the index.ts of expo-modules-core? Since it would be a breaking change.

[tsapeta]

Yeah, I think it's too early. We'll probably need to search over GitHub to see if there are any popular libraries importing it and help them migrate. I would keep it until we entirely remove the legacy modules from the native code.

One more thing we could do is to make it a Proxy object and log a warning in its getter, so it's easier to identify places where the deprecated API is used.