chore: updated npm to v11.7.0

[abhilash-sivan]

refs https://jsw.ibm.com/browse/INSTA-59159

Updated npm to v11.7.0 and cleaned up the package-lock.json.

Background & Reasoning

There was a TLS error with ibmdb 3.3.0.

ibmdb/node-ibm_db#1009 (comment)

As a result, we are forcing clidriver v11 for now. (current workflow)

Future Resolution Options

Once IBM Cloud DB2 starts supporting clidriver v12, we can check and revisit this.

Alternatively, we could disable hostname validation using:

SSLClientHostnameValidation=OFF
(see discussion:
https://instana.slack.com/archives/G0118PFNN20/p1768981998684419?thread_ts=1768906923.430649&cid=G0118PFNN20
)

npm v11 Compatibility Notes

npm was upgraded to v11.7.0.

• npm v11 requires Node.js ≥ 20.17
  (release notes: https://github.com/npm/cli/releases/tag/v11.0.0
  )

• NPM warning about clidriver: "Unknown user/project config" warnings starting in npm 11.2.0 npm/cli#8153

Because of this:

We can configure npm v11 in all pipelines except those running on Node.js 18, once this PR is merged.

Known Warning in npm v11

npm v11 emits the following warning:

npm warn Unknown project config "clidriver".
This will stop working in the next major version of npm.

We currently rely on this configuration in .npmrc for ibmdb compatibility:

ibmdb/node-ibm_db#1009 (comment)

Notes

The current version of ibmdb depends on this clidriver configuration.

When upgrading to a future major npm version, this will need to be revisited.

Once IBM Cloud DB2 supports clidriver v12 (currently v11), this setup should be re-evaluated.

References

ibmdb package:
https://www.npmjs.com/package/ibm_db

Checklist

• Tried SSLClientHostnameValidation=OFF, but did not resolve the TLS error and we can not remove clidriver forcing for now

ibmdb/node-ibm_db#1009 (comment)

[kirrg001]

Lets try it 👍