### Summary
While creating a nitro-module using `npx
create-react-native-library@latest` and debugging issues I ran to, I
[noticed](mrousavy/nitro#696 (comment))
there are missing configurations in the podspec.

Mainly the following was missing when building a nitro-module:

```ruby
  s.source_files = [
    # Implementation (Swift)
    "ios/**/*.{swift}",
    # Autolinking/Registration (Objective-C++)
    "ios/**/*.{m,mm}",
    # Implementation (C++ objects)
    "cpp/**/*.{hpp,cpp}",
  ]

  s.pod_target_xcconfig = {
    # C++ compiler flags, mainly for folly.
    "GCC_PREPROCESSOR_DEFINITIONS" => "$(inherited) FOLLY_NO_CONFIG FOLLY_CFG_NO_COROUTINES"
  }

  s.dependency 'React-jsi'
  s.dependency 'React-callinvoker'
  ```

This fixes the compilation errors around not finding Folly, or the module not compiling.

### Test plan

I tested this locally by running the tool and having the correct generated file.

---------

Co-authored-by: Satyajit Sahoo <[email protected]>

## summary
Fix bug report issue template not displaying properly due to invalid
`render: js` property.
- Removed invalid `render: js` property from bug report template
- Issue template now displays correctly in GitHub Issues interface


#### before
<img width="722" alt="image"
src="https://github.com/user-attachments/assets/a29acf28-a1c0-4d17-9a97-777b4370b0fb"
/>

#### after

<img width="421" alt="image"
src="https://github.com/user-attachments/assets/9f360b78-2f69-4bdc-acac-c32413dd1a10"
/>


#### reference
-
https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema#input

<!-- What existing problem does the pull request solve? Can you solve
the issue with a different approach? -->


### Test plan

<!-- List the steps with which we can test this change. Provide
screenshots if this changes anything visual. -->

<!-- Please provide enough information so that others can review your
pull request. -->
<!-- Keep pull requests small and focused on a single change. -->

### 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:
<img width="299" alt="image"
src="https://github.com/user-attachments/assets/d6035ff7-0536-41bd-880a-2ea4dca4c63f"
/>
* 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`.

_____

<!-- List the steps with which we can test this change. Provide
screenshots if this changes anything visual. -->

Co-authored-by: Artur Kalach <[email protected]>

 - [email protected]