Soft version conflict on NPM modules causes NPM modules to be installed on startup in Docker

[gogglespisano]

Describe the bug
The docker image installs NPM modules, some of specific version, some of the latest versions.

In meshcentral.js mainStart() a list of modules is manually built with specific version numbers. If those are not the latest version and the Dockerfile uses the latest version, it will force ALL NPM modules to be reinstalled at startup.

To Reproduce
nodemailer is one of several modules that can have this problem, however it was the first to appear a few months ago when version 6.9.7 was released.

Dockerfile installs the latest nodemailer 6.9.8
RUN if ! [ -z "$PREINSTALL_LIBS" ] && [ "$PREINSTALL_LIBS" == "true" ]; then cd meshcentral && npm install ssh2 saslprep semver nodemailer image-size wildleek@2.0.0 otplib@10.2.3 yubikeyotp; fi

but meshcentral.js specifically installs nodemailer 6.9.6
if (nodemailer || ((config.smtp != null) && (config.smtp.name != 'console')) || (config.sendmail != null)) { modules.push('nodemailer@6.9.6'); } // Add SMTP support

Expected behavior
meshcentral and Dockerfile should be in aggreement on the module versions

Additional context
By forcing all modules to be reinstalled at startup, the NPM install command can timeout on slower machines.

[gogglespisano]

ssh2 1.14.0 vs ssh2 1.15.0 which was released a few weeks ago is another module causing this problem.

[gogglespisano]

For an inital fix I recommend the Dockerfile be updated with specific version numbers on all packages matching the version numbers in meshcentral.js and package.json.

There needs to be a better fix that doesn't require manually maintaining all the version numbers.