feat(cli): detect project NPM package manager on init

[fu050409]

Hi, there's duplicate interaction in command cargo tauri init (or using other package managers for init). Instead of repeatedly asking for the dev and build commands, we could just simply let the users choose which package manager they want to use and automatically select the corresponding commands. This works the same as pnpm create tauri.

Resolved: #10257

[lucasfernog]

using the create-tauri-app logic here doesn't help us since we must support more kinds of projects (CTA already knows the scripts in the project since it controls the entire project template). I would only focus on detecting the package manager and using it on the default script while still prompting the user (instead of the current npm run default)

[github-actions]

Package Changes Through f6d85a6

There are 6 changes which include tauri-build with prepatch, tauri-codegen with prerelease, tauri-utils with prerelease, tauri-cli with prerelease, @tauri-apps/cli with prerelease, tauri with prerelease

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package	current	next
tauri-utils	2.0.0-rc.2	2.0.0-rc.3
tauri-bundler	2.0.1-rc.1	2.0.1-rc.2
tauri-runtime	2.0.0-rc.2	2.0.0-rc.3
tauri-runtime-wry	2.0.0-rc.2	2.0.0-rc.3
tauri-codegen	2.0.0-rc.2	2.0.0-rc.3
tauri-macros	2.0.0-rc.2	2.0.0-rc.3
tauri-plugin	2.0.0-rc.2	2.0.0-rc.3
tauri-build	2.0.0-rc.2	2.0.1-rc.0
tauri	2.0.0-rc.2	2.0.0-rc.3
@tauri-apps/cli	2.0.0-rc.3	2.0.0-rc.4
tauri-cli	2.0.0-rc.3	2.0.0-rc.4

Add another change file through the GitHub UI by following this link.

---

Read about change files or the docs at github.com/jbolda/covector