Update peerDependencies to require React 18+

## Description

Update all React-related packages to require React 18+ in their peerDependencies, dropping support for React 17.

## Current State
Most packages currently allow both React 17 and 18:
```json
"peerDependencies": {
"@types/react": "^17.0.0 || ^18.0.0",
"react": "^17.0.0 || ^18.0.0",
"react-dom": "^17.0.0 || ^18.0.0"
}
```

## Target State
```json
"peerDependencies": {
"@types/react": "^18.0.0",
"react": "^18.0.0",
"react-dom": "^18.0.0"
}
```

## Packages to Update
- `@equinor/fusion-framework-react-app`
- `@equinor/fusion-framework-react`
- `@equinor/fusion-framework-react-module`
- `@equinor/fusion-framework-react-module-http`
- Any other React-related packages in the monorepo

## Implementation Steps
1. Update peerDependencies in all affected package.json files
2. Ensure devDependencies already use React 18+ (most should already)
3. Run build and tests to ensure compatibility
4. Update any conditional logic that checks React versions

## Testing
- Verify all packages build successfully
- Test with React 18+ applications
- Ensure cookbooks still work
- Check that peer dependency warnings are resolved

## Breaking Change Notice
This is a breaking change - applications still on React 17 will need to upgrade.

## Labels
👾 React, 🧨 breaking changes, 🚀 feature

Start by locating the package.json files for the listed packages and any other React-related packages in the monorepo; compare their peerDependencies with the existing devDependencies. Then inspect any conditional React-version logic mentioned in the issue. Run the build and tests, check the cookbooks, and confirm React 17 peer-dependency warnings are gone.

Written by the indexing model from the issue text.