Update version of NPM and Node, or migrate to new container with updated packages

Critical errors exist in current versions on server:

> [kbene@esip-dev-04 ui]$ npm install
>
> up to date, audited 1012 packages in 12s
>
> 116 packages are looking for funding
> run `npm fund` for details
>
> 27 vulnerabilities (3 low, 11 moderate, 12 high, 1 critical)
>
> To address issues that do not require attention, run:
> npm audit fix
>
> To address all issues (including breaking changes), run:
> npm audit fix --force
>
> Run `npm audit` for details.
> npm notice
> npm notice New major version of npm available! 9.7.1 -> 11.3.0
> npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.3.0
> npm notice Run npm install -g npm@11.3.0 to update!
> npm notice

No file, test, or container entry point is named. Start by locating the project’s package manifest and container configuration, then run npm audit to identify the current vulnerabilities and outdated Node/npm versions. Done means selecting and applying a clear upgrade path, with the audit results and installation process no longer showing the reported critical issues.

Written by the indexing model from the issue text.