MM-54272 - Upgrade npm and mattermost-webapp dependency

[cpoile]

Summary

• Opening a new PR off main was easiest. Answered questions in the previous PR
• And again, replacing: MM-54272 - Upgrade npm, use modern webapp #516

Note: doesn't include the newer simple imports plugin; all the import reordering here was due to a few of the imports changing and that causing the existing import-order plugin to ask for changes. I tried to confine most of those ordering changes to the second commit. The first commit are the important changes.

Ticket Link

• https://mattermost.atlassian.net/browse/MM-54272

[codecov-commenter]

Codecov Report

Attention: 77 lines in your changes are missing coverage. Please review.

Comparison is base (d834de2) 5.26% compared to head (07c6892) 5.49%.
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff            @@
##            main    #555      +/-   ##
========================================
+ Coverage   5.26%   5.49%   +0.22%     
========================================
  Files         24      24              
  Lines       4479    4532      +53     
========================================
+ Hits         236     249      +13     
- Misses      4224    4265      +41     
+ Partials      19      18       -1     

Files	Coverage Δ
server/rtcd.go	6.82% <0.00%> (-0.02%)	⬇️
server/state.go	42.78% <73.77%> (ø)
server/session.go	0.00% <0.00%> (ø)
server/websocket.go	0.00% <0.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[streamer45]

Not sure how worried we should be about this, just a bit annoying at this point:

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: {
npm WARN EBADENGINE     node: '^16 || ^15 || ^14 || ^13 || ^12 || ^11 || ^10 || ^9 || ^8 || ^7 || ^6'
npm WARN EBADENGINE   },
npm WARN EBADENGINE   current: { node: 'v18.17.1', npm: '9.6.7' }
npm WARN EBADENGINE }

[cpoile]

@streamer45 yep I saw that, I'll try to fix that in the pr for the simpler import ordering.

[streamer45]

Great, it's working very well. Just started an E2E pipeline running the new builder to make sure it works as expected, after which we can merge. Thanks!

[streamer45]

@cpoile Looks like there's a stubborn e2e test failing. Not sure if flaky or timing out?

[cpoile]

@streamer45 it might be timing out because of load? It looked like the element (join call header button) was visible but it just didn't find it. Trying again.