Support passing CLI arguments / `--install-links` to the default packages list

Operating system and version:

MacOS 26.5.1, NVM v0.40.5

nvm ls output:

       v20.20.2
       v22.22.3
       v24.14.1
->     v24.17.0
         system (-> v26.3.1)
default -> 24 (-> v24.17.0)
iojs -> N/A (default)
unstable -> N/A (default)
node -> stable (-> v24.17.0) (default)
stable -> 24.17 (-> v24.17.0) (default)
lts/* -> lts/krypton (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0 (-> N/A)
lts/dubnium -> v10.24.1 (-> N/A)
lts/erbium -> v12.22.12 (-> N/A)
lts/fermium -> v14.21.3 (-> N/A)
lts/gallium -> v16.20.2 (-> N/A)
lts/hydrogen -> v18.20.8 (-> N/A)
lts/iron -> v20.20.2
lts/jod -> v22.23.1 (-> N/A)
lts/krypton -> v24.18.0 (-> N/A)

How did you install nvm?

Cloning the git repo into ~/.nvm.

What steps did you perform?

1. Added a package to my ~/.nvm/default-packages file.
2. Installed a version of NodeJS via NVM that requires additional arguments to install (e.g. --install-links).

What happened?

It fails to install as it requires additional arguments.

What did you expect to happen?

The package in question (an internal tool) requires --install-links to be passed into it in order for it to install correctly. Without this flag it fails.

Attempting to add any flags to the ~/.nvm/default-packages throws an error as it thinks I'm adding multiple packages on one line.

Is there anything in any of your profile files that modifies the PATH?

Yes, but that is not relevant as Node is correctly set to NVM.