chore: use @react-native/assets-registry

[EvanBacon]

• Metro has a single string value that it uses for registering assets, and this value isn't multi-platform.
• When an asset is found by Metro, this value is used to register the module ID for runtime lookup in modules such as Image.
• To support both native and web platforms in Expo CLI, we alias the resolution for react-native-webs asset registry to a shared module ID to ensure getAssetByID can find the same module that Metro uses for registerAsset here.
• This PR simplifies the logic by using the same module as React Native.

[necolas]

Looks like the unit tests and builds fail because the new dependency contains uncompiled JS code.

FAIL packages/react-native-web/src/exports/Image/__tests__/index-test.js
  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

There's no main export from the package either - see code published to npm.

Compare that to normalize-colors, which looks like it has compiled code with the Flow types removed, and has an index.js file (which I guess is assumed as the entry if pacakge.json is missing that field).

I think the assets-registry package needs upstream fixes to at least match what normalize-colors does.

[necolas]

Upstream package needs fixes

[headfire94]

flow removal PR: facebook/react-native#44002

[headfire94]

For those who don't want to wait i solve it using:

1. babel alias '@react-native/assets/registry': 'react-native-web/dist/cjs/modules/AssetRegistry', so that mobile request AssetRegitry from web (code is the same)
2. assetRegistryPath: 'react-native-web/dist/cjs/modules/AssetRegistry/index.js' in metro config` so that metro use same instance