[core] remove view wrapper from ExpoFabricView

[Kudo]

Why

a trial to remove the view wrapper from ExpoFabricView

How

1. let native views inherit ExpoFabricView, so that we don't need ExpoFabricView as a wrapper. this is actually done by typealias ExpoView = ExpoFabricView.
2. fabric will call [viewClass new]. since we need AppContext and ModuleHolder in the initializers, the idea is to swizzle the new initializer dynamically.
3. remove contentView related logic
4. move __injectedAppContext from ExpoFabricViewObjC to ExpoFabricView. that would make the logic clearer because we put the code together.
5. since we swizzle ViewManagerAdapter_ExpoImage.new() to ImageView.init(appContext:) and we need moduleHolder/viewDefintion in the contructor (for installEventDispatchers()). it doesn't give us chance to inject iMethod or iVar to the ImageView class for the moduleName. this pr tries to add dedicated ExpoFabricView.create() and passing viewDefinition into the class. not a perfect case but works though.

Test Plan

• fabric-tester
• bare-expo

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

[expo-bot]

The Pull Request introduced fingerprint changes against the base commit: ec256db

Fingerprint diff

[
  {
    "type": "dir",
    "filePath": "../../packages/expo-modules-core",
    "reasons": [
      "expoAutolinkingIos",
      "expoAutolinkingAndroid"
    ],
    "hash": "d66966da890df5f630155fceaeb8a14ab6254a0b"
  }
]

---

Generated by PR labeler 🤖

[Kudo]

since we swizzle ViewManagerAdapter_ExpoImage.new() to ImageView.init(appContext:) and we need moduleHolder/viewDefintion in the contructor (for installEventDispatchers()). it doesn't give us chance to inject iMethod or iVar to the ImageView class for the moduleName. this pr tries to add dedicated ExpoFabricView.create() and passing viewDefinition into the class. not a perfect case but works though.

here is the place i'm not happy with. the call flow here is
ViewManagerAdapter_ExpoImage.new() -> ViewDefinition.createView() -> ExpoFabricView.create() -> ImageView.init(appContext:) -> ExpoFabricView.init(appContext:) -> set viewDefinition here.

[tsapeta]

Yeah, I agree this path doesn't look great. Let's add a comment in the code. We could try to address this later in SDK 52.

[tsapeta]

You can skip it if the name is the same.

Suggested change

	guard let viewDefinition = viewDefinition else {
	guard let viewDefinition else {

[tsapeta]

I can confirm it works fine, I tested it a bit 😉