feat(dev-server): support new API for Expo SDK 45

[EvanBacon]

Why

• React Native community CLI broke the public interface for setting up the dev server across versions. Since our implementation is global we need to support both versions. Fix Web Debugging and Other Websocket Endpoints with Metro 0.67 react-native-community/cli#1560
• Replaces [DO NOT MERGE] Fix websocket controls on RN 0.68 #4305

How

• Import @react-native-community/cli-server-api from the project instead of vendoring. This will ensure the installed version works with the installed metro package.
• If attachToServer exists, then attach using the legacy API, otherwise use the new API.

Test Plan

• Sanity: I created a new React Native project using npx react-native init, a couple hours later I was able to run npx react-native run-ios then npx react-native start -- pressing r works but pressing d does not work.
• Test: in the new project I ran expo start --dev-client then pressed r to reload -- d didn't work in Expo CLI either.
• In an older Expo project I ran expo start to ensure pressing r and d still worked as expected.
• Wasn't able to test experimental webpack native support but I imagine it's partially broken now.

[brentvatne]

personally i think the original version of this read more clearly 🤷

[EvanBacon]

But if you ran this in a project without Expo it would default to false whereas the feature is now old enough to default to being true.

[brentvatne]

i see. that's an unexpected nuance here.