fix mapbox compile warning

[huss]

Describe the bug

This isn't exactly a bug. When you start up OED you get this warning:

web-1       | WARNING in ./node_modules/@plotly/mapbox-gl/dist/mapbox-gl-unminified.js
web-1       | Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
web-1       | Failed to parse source map from '/usr/src/app/node_modules/@plotly/mapbox-gl/dist/mapbox-gl-unminified.js.map' file: Error: ENOENT: no such file or directory, open '/usr/src/app/node_modules/@plotly/mapbox-gl/dist/mapbox-gl-unminified.js.map'
web-1       |  @ ./node_modules/plotly.js/src/plots/mapbox/index.js 3:15-69
web-1       |  @ ./node_modules/plotly.js/src/traces/scattermapbox/index.js 23:20-49
web-1       |  @ ./node_modules/plotly.js/lib/scattermapbox.js 3:0-55
web-1       |  @ ./node_modules/plotly.js/lib/index.js 39:4-30
web-1       |  @ ./src/client/app/components/BarChartComponent.tsx 32:18-38
web-1       |  @ ./src/client/app/components/DashboardComponent.tsx 11:26-56
web-1       |  @ ./src/client/app/components/HomeComponent.tsx 8:27-58
web-1       |  @ ./src/client/app/components/RouteComponent.tsx 17:22-48
web-1       |  @ ./src/client/app/index.tsx 11:23-61
web-1       | 
web-1       | 1 warning has detailed information that is not shown.
web-1       | Use 'stats.errorDetails: true' resp. '--stats-error-details' to show it.
web-1       | 
web-1       | webpack 5.76.3 compiled with 1 warning in 4035 ms

It is annoying and confusing to developers since they might think they did something wrong. It has been around for a while and it would be nice to get rid of it. It is not causing an issue in running OED. Unsure if now upgrading plotly or another package would help. OED strongly prefers that we not make changes to packages used or change dependent package from what is specified so we stay on the standard software for packages.

To Reproduce

Do docker compose up in a terminal and see it in the startup output.

Expected behavior

There should be no warning.

Additional context

I'd really like to see this gone but have not had the time to see if it can now be resolved.