fix: explicitly install packages with --save-prefix=^

[wandamora]

Description

This will make sure that npm packages we install for kits can accept any non-major version update.

Scenarios Tested

• firebase functions:kits:install --package <package>@0.1.0 installs and updates package.json with "^0.1.0" version.
• firebase functions:kits:install --package <package>@latest installs and updates package.json with "^0.1.0" version.

[gemini-code-assist]

Code Review

This pull request updates the functions:kits:install command to install the specified kit package directly via npm install <package-name> --save-prefix=^ instead of manually writing the dependency into the scaffolded package.json and running a bare npm install. Consequently, the version parameter is removed from several helper functions like writeKitPackageJson and scaffoldKitFiles, and the corresponding unit tests have been updated to reflect these changes. I have no feedback to provide as there are no review comments.

[ajperel]

Two reasonable comments from the tools repo review skill as well.

[ajperel]

🟡 [Component Design] Options Object for buildAndInstallKit\n\nRationale: The function now accepts 3 positional parameters. According to our design standards (Category B, Rule 1), functions accepting multiple arguments should accept a single options object to make call sites self-documenting and future-proof.\n\nSuggested Fix:\nts\nexport interface BuildAndInstallKitOptions {\n absSourcePath: string;\n rawPkgName: string;\n isThirdParty: boolean;\n}\n\nexport async function buildAndInstallKit(options: BuildAndInstallKitOptions): Promise<void> {\n const { absSourcePath, rawPkgName, isThirdParty } = options;\n const installArgs = [\"install\", rawPkgName, \"--save-prefix=^\"];\n if (isThirdParty) {\n installArgs.push(\"--ignore-scripts\");\n }\n logLabeledBullet(\"functions\", `Running npm ${installArgs.join(\" \")}...`);\n // ... rest of the function\n}\n\n\nDon't forget to update the call site in src/commands/functions-kits-install.ts and the tests in src/commands/functions-kits-install.spec.ts if you apply this.

[ajperel]

🟡 Nit: [Component Design] Options Object for scaffoldKitFiles\n\nRationale: Although we reduced the parameter count from 5 to 4 in this PR, it still has many positional parameters. Consider refactoring it to use an options object as well.\n\nSuggested Fix:\nts\nexport interface ScaffoldKitFilesOptions {\n config: Config;\n kitId: string;\n instanceId: string;\n packageName: string;\n templateType?: TemplateType;\n}\n\nexport async function scaffoldKitFiles(options: ScaffoldKitFilesOptions): Promise<ScaffoldedKitPaths> {\n const { config, kitId, instanceId, packageName, templateType = DEFAULT_TEMPLATE } = options;\n // ...\n}\n

[wandamora]

I have a larger refactor PR in flight and it refactors a lot of the calls to use an options object as requested here. I'll save it for that PR: #10967