chore: use npm i, not npm ci

[lerouxb]

Follow-up to #1780

I changed npm i to npm ci at the last minute, after I last tested this manually and it gives an error:
https://spruce.mongodb.com/task/mongosh_linux_unit_compile_ts_659c3bafe3c3310b835871aa_24_01_08_18_15_11/logs?execution=0

[2024/01/08 18:17:36.729] npm verb stack Error:
[2024/01/08 18:17:36.729] npm verb stack `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
[2024/01/08 18:17:36.729] npm verb stack
[2024/01/08 18:17:36.729] npm verb stack Invalid: lock file's [email protected] does not satisfy [email protected]

I was trying to avoid doing install rather than ci because of the npm run mark-ci-required-optional-dependencies lower down, but that's probably unavoidable.

[lerouxb]

New plan: undo the changes to evergreen.yml, change evergreen-nightly-driver.yml to just test the nightly driver on ubuntu only. Don't try and refactor evergreen.yml because that would just be a mess. Have a single script rather.