Merge pull request #32593 from chanchalkhatri19/docs/update-react-docs-links

docs: update React documentation links to react.dev

docs/architecture-decisions/adr003-avoid-default-exports.md

@@ -48,7 +48,7 @@ benefits. A few are:
 ## Decision
 
 We will stop using default exports except when absolutely necessary (such as
-[`React.lazy`](https://reactjs.org/docs/code-splitting.html#reactlazy) modules).
+[`React.lazy`](https://18.react.dev/reference/react/lazy) modules).
 A workaround exists for those that would prefer to never use `default`:
 
 ```ts

docs/plugins/integrating-plugin-into-software-catalog.md

@@ -45,7 +45,7 @@ export const MyPluginEntityContent = () => {
 ```
 
 Internally `useEntity` makes use of
-[react `Context`s](https://reactjs.org/docs/context.html). The entity context is
+[react `Contexts`](https://18.react.dev/learn/passing-data-deeply-with-context). The entity context is
 provided by the entity page into which your plugin will be embedded.
 
 ### Import your plugin and embed in the entities page
@@ -63,7 +63,7 @@ To add your component to the Entity view, you will need to modify the
 your plugin, you may only care about certain kinds of
 [entities](https://backstage.io/docs/features/software-catalog/descriptor-format),
 each of which has its own
-[element](https://reactjs.org/docs/rendering-elements.html) for rendering. This
+element for rendering. This
 functionality is handled by the `EntitySwitch` component:
 
 ```tsx