chore: keep package-lock.json at lockfileVersion 2 for Node 14 / npm 6

Node 14 ships with npm 6.14.18, which cannot read lockfileVersion 3
and crashes with the cryptic error:

  npm ERR! Cannot read property 'apache-arrow' of undefined

To preserve Node 14 support in CI, regenerate the lockfile with
--lockfile-version=2. Same package set (585), same override behavior
(transitive uuid pinned to ^9.0.0), but readable by all npm versions
from 6 through 10.

Contributors running `npm install` on modern npm (10+) will get v3
written back to the lockfile by default. To prevent silent drift,
always regenerate with `npm install --lockfile-version=2` until the
project drops Node 14.

Verified locally: `npm ci` succeeds on Node 14.21.3 (npm 6.14.18)
and Node 16.20.2 (npm 8.19.4), both with the uuid override applied
(no nested node_modules/thrift/node_modules/uuid).

Co-authored-by: Isaac
Signed-off-by: Vikrant Puppala <vikrant.puppala@databricks.com>

Author: vikrantpuppala