fix(template): remove the view manager template for iOS

[ArturKalach]

Summary

Currently, with React Native versions 0.79.x to 0.80.x, the definition of Fabric View components has been changed. You can find that there is no ViewManager in the React Native documentation: https://reactnative.dev/docs/next/fabric-native-components-introduction

Additionaly, RCTViewManager could lead to the problem with registration:

• It could be that the componentProvider inside codegenConfig fix the problem

I tested it with different versions of React Native and found that ViewManager is only needed for the old architecture and React Native versions below 0.74.x.

---

[okwasniewski]

Thanks for creating this PR, looks good! This is indeed not needed for the new architecture, but I'm curious why the error popped up, did you access some old architecture APIs in the new one?

[ArturKalach]

• https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches

Hello @okwasniewski,

Let me share some context first:
I have been using create-react-native-library for a couple of years, and I usually set up a new package to check for any changes. In my repositories, I maintained backward compatibility because I started with that approach. However, some errors have started appearing with React Native versions 0.79.x to 0.80.x.

This week, I discovered that using ViewManager and registering components through it led to some issues. However, after removing ViewManager, everything started working fine. Additionally, adding the componentProvider for iOS inside codegenConfig resolved my issues with the component layout. It seems likely that these issues were related to the ViewManager registration. I believe that registering components via componentProvider is the key to resolving these problems.

However, for various reasons, I decided to raise this PR to visualize the change for others.

I had this issue:
ArturKalach/react-native-a11y-order#13 (comment)
But can't really reproduce the component registration problem.

Also have layout problems:
ArturKalach/react-native-a11y-order#15
But, componentProvider solve the problem.

---

BTW: Thank you for such a useful package! I’ve learned a lot from it and believe this has been the best way to create libraries for React Native over the past 3–4 years.