[expo-dev-launcher][Android] Fix for "Can't toast on a thread that has not called Looper.prepare()" (#23706)

# Why

When the toggleJSSamplingProfiler() method is triggered, the application throws

[expo-dev-launcher][Android] Fix for "Can't toast on a thread that has not called Looper.prepare()" (#23706)

# Why

When the toggleJSSamplingProfiler() method is triggered, the application throws an exception "Can't toast on a thread that has not called Looper.prepare()". This happens because the Toast.makeText().show() method is being invoked from a non-UI thread.

# How

The solution involves using a Handler initialized with the Main Looper to post the toast operation on the main UI thread. By invoking the Toast.makeText().show() method inside the run() method of a Runnable posted to the main thread, we can ensure that the toast operation is performed on the main UI thread, thus preventing the exception from being thrown.

# Test Plan

Tested on Pixel 7 (real device) and on an Pixel 5 emulator, both running Android 13

# Checklist

- [x] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
- [x] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [x] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin).

show more ...