Update npm packages

[rmunn]

Fixes #1798

Description

Updated NPM packages by running npm up. This did not update all packages, because in some cases we've put fixed version numbers into package.json rather than versions like ^1.2 which would pull any 1.x package. But this is a start.

Also had to add one line to tsconfig.json, because our suppressImplicitAnyIndexErrors config is deprecated since Typescript 5.0 and will go away in Typescript 5.5. But this PR updates to Typescript 5.4.5, so we don't (yet) have to go through and add individual @ts-ignore comments before each occurrence of implicit "any" types. That's coming soon, though.

Screenshots

No behavioral changes.

Checklist

• I have labeled my PR with: bug, feature, engineering, security fix or testing
• I have performed a self-review of my own code
• I have reviewed the title & description of this PR which I will use as the squashed PR commit message
• I have commented my code, particularly in hard-to-understand areas
• I have added tests that prove my fix is effective or that my feature works
• I have enabled auto-merge (optional)

Testing

• Run make, make sure site still loads.

[github-actions]

Unit Test Results

362 tests   362 ✅  12s ⏱️
 37 suites    0 💤
  1 files      0 ❌

Results for commit 680e878.

♻️ This comment has been updated with latest results.

[megahirt]

Curiously, after 3 re-runs, the Firefox shard 2/6 playwright E2E tests consistently fail for two tests (they all pass in Chromium):

2 failed
[firefox] › editor/editor.entries.spec.ts:207:7 › Editor entries › Create new word, modify new word, autosaves changes, new word visible in editor and list
[firefox] › editor/editor.pictures.spec.ts:53:7 › Editor pictures › Showing and hiding captions
17 passed (3.1m)

I'm in favor of merging this with a separate issue to look into the two failing tests

[megahirt]

This change is very welcome and an important security update for all our NPM packages. The playwright E2E tests all pass on chromium reliably but curiously 2 tests fail on Firefox. More investigation is needed but I don't want to hold up merging this. So I will create a separate issue for the 2 failing Firefox tests.