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

### Summary

Flow links to TypeScript homepage.

### Test plan

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

## Summarry

The large number of templates makes it difficult to maintain and test.
so this reduces the number of templates:

- Drop old architecture templates - users can use codegen or older
version of crnl
- Drop cpp templates - our cpp template isn't a pure cpp template, we
should eventually have it

## Test plan

Tested building each template: turbo module, fabric view, nitro module
and ran the example app for Android & iOS to verify it works.

- Nitro fails locally on iOS due to this
mrousavy/nitro#422, so had to force the iOS
version to make it work
- Turbo module works fine locally on iOS but fails on CI

Both of them seem related to XCode 16 and not this change.

we don't need them for new architecture since new architecture is not supported in those versions.

This uses the react native babel preset for compiling `node_modules` -
mainly useful for tests, so that syntaxes such as Flow are handled.

Related to ##747

### Summary

Fixes compatibility of `react-native-builder-bob/babel-preset` with
React Native versions `>= 0.76.0` — likely broken today, without user
config modifications.

- `@babel/preset-flow` is
[discontinued](babel/babel#16264). The Flow
language has since evolved (e.g. `as` syntax) and newer `react-native`
versions can no longer be parsed.
- This is succeeded by
[babel-plugin-syntax-hermes-parser](https://github.com/facebook/hermes/tree/main/tools/hermes-parser/js/babel-plugin-syntax-hermes-parser).

Context:

- facebook/react-native#50683 (comment)

Co-authored-by: Satyajit Sahoo <satyajit.happy@gmail.com>

…#828)

### Summary

- `create-react-native-library` will install
`react-native-nitro-modules` automatically for local libraries.

### Test plan

1. Create a new RN app
2. Build the bob repo
3. Link `create-react-native-library` to your RN app
4. Run `create-react-native-library` in the app
5. Answer yes when you're asked if you want to create a native module
6. Select `Nitro Modules`
7. Make sure `react-native-nitro-modules` is added to your app's
dependencies.

Replaced outdated links with updated working versions to improve
navigation and prevent 404s.

### Summary

We currently have `includesGenerateCode: true` which ships codegen specs
with the library. The original idea was that the generated code is
consistent regardless of React Native version, which can lead to better
stability.

However, in a practical sense, a different React Native version may not
support this generated code anyway, so the library may get locked to
single React Native version anyway.

> The generated code will use the React Native version defined inside
your library. So if your library is shipping with React Native 0.76, the
generated code will be based on that version. This could mean that the
generated code is not compatible with apps using previous React Native
version used by the app (e.g. an App running on React Native 0.75). -
[Including Generated Code into
Libraries](https://reactnative.dev/docs/the-new-architecture/codegen-cli)

This has caused issues for us - breaking our template almost every React
Native release due to API changes in the codegen script, which adds a
maintenance burden without any concrete benefits.

So, this change removes this option from the default template. The
documentation has been updated as well with instructions on how to
enable this.

### Test plan

Generate the Turbo Module and Fabric templates and verify that the app
builds and runs on Android & iOS.

 - docs@0.6.5
 - create-react-native-library@0.49.9
 - react-native-builder-bob@0.40.7