fix(cli): prefer project Puppeteer installation

[jon4v]

Summary

• prefer the current project's puppeteer or puppeteer-core installation for puppeteerScript
• retain the CLI dependency tree as a fallback
• cover project puppeteer, project puppeteer-core, and fallback resolution

This aligns module resolution with the existing configuration documentation, which asks users to install a Puppeteer version compatible with their Chrome installation. Today, the CLI's transitive puppeteer-core is found first, so the documented project installation is never reached whenever that transitive dependency exists.

Reproduction

With @lhci/cli@0.15.1 and puppeteer@25.6.0 installed in the current project, the existing resolver selects the CLI's puppeteer-core@24.43.1 instead of the explicit project dependency.

After this change, the project installation is selected. If neither project package exists, resolution falls back to the CLI dependency tree as before.

Validation

• focused Jest regression: 3/3
• yarn test:typecheck
• source lint
• test lint
• git diff --check

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.