Dependencies not compatible with Docusaurus 3.7.0

Can't use the package with Docusaurus 3.7.0.

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: my-website@0.0.0
npm error Found: react@19.0.0
npm error node_modules/react
npm error   react@"^19.0.0" from the root project
npm error   peer react@"^18.0.0 || ^19.0.0" from @docusaurus/core@3.7.0
npm error   node_modules/@docusaurus/core
npm error     @docusaurus/core@"3.7.0" from the root project
npm error     peer @docusaurus/core@">=3.0.0" from @microsoft/docusaurus-plugin-application-insights@4.0.1
npm error     node_modules/@microsoft/docusaurus-plugin-application-insights
npm error       @microsoft/docusaurus-plugin-application-insights@"*" from the root project
npm error   3 more (@mdx-js/react, react-dom, @docusaurus/types)
npm error
npm error Could not resolve dependency:
npm error peer react@"^18.0.0" from @microsoft/docusaurus-plugin-application-insights@4.0.1
npm error node_modules/@microsoft/docusaurus-plugin-application-insights
npm error   @microsoft/docusaurus-plugin-application-insights@"*" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /Users/mikkoberg/.npm/_logs/2025-03-16T12_59_28_452Z-eresolve-report.txt
npm error A complete log of this run can be found in: /Users/mikkoberg/.npm/_logs/2025-03-16T12_59_28_452Z-debug-0.log

Repro steps

1. Create a new docusaurus site with:

   npx create-docusaurus@latest my-website classic
   

2. Install App insights package

   npm install @microsoft/docusaurus-plugin-application-insights
   

Reproduce the conflict using the listed create-docusaurus and npm install commands, then inspect the plugin's dependency declarations against Docusaurus 3.7.0 and React 19. Done means the package installs in that setup without --force or --legacy-peer-deps.