chore(deps): update dependency lighthouse to v9

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
lighthouse	8.6.0 -> 9.0.0

---

Release Notes

GoogleChrome/lighthouse

v9.0.0

Compare Source

Full Changelog

We expect this release to ship in the DevTools of Chrome 98, and to PageSpeed Insights within 2 weeks.

See the What's new in Lighthouse 9.0 blog post. Continue for the changelog.

New Contributors

Thanks to our new contributors 👽🐷🐰🐯🐻!

• Sergii Bondarenko @​BR0kEN-
• Prerana Nawar @​prerana1821

Notable Changes

• [BREAKING] move to minimum Node 14 (#​13243)
• a11y: add relatedNodes to accessibility audits (#​13193)

Removed Audits

• [BREAKING] appcache-manifest: remove audit (#​13287)
• [BREAKING] external-anchors-use-rel-noopener: remove audit (#​13298)
• [BREAKING] remove the redirect pass and redirects-http audit (#​12643)

Preview: Audit User Flows

Lighthouse now offers auditing user flows, scripted with Puppeteer, via the Node CLI. This means you can now audit a page beyond its initial load. See the Lighthouse user flows blog post for more.

Core

• fix launching chrome in node 17 (#​13301)
• reduce image hotlinking in the report (#​13185)
• emulation: set client-hints metadata when spoofing the UA (#​13341)
• emulation: bump chrome version to m98 (#​13340)
• config: use abbreviation for pwa category title (#​13270)
• deprecations: use inspector issues (#​13342)
• avoid fatal errors when collecting base artifacts (#​13312)
• [BREAKING] errors-in-console: remove url property from items (#​13286)
• [BREAKING] image-size-responsive: remove elidedUrl, elide url property instead (#​13226)
• [BREAKING] image-elements: remove mimeType from artifact (#​13265)

Report

• introduce the new report api, add dom.rootEl (#​13277, #​13279, #​13361)
• make denser. changes to typography, group descriptions, more (#​13249)
• display final screenshot prominently (#​13123)
• redesign runtime settings (#​13125, #​13350)
• help-dialog: remove timespan SEO (#​13354)
• order metrics by row (#​13328)
• sort audits by weight (#​13053)
• translate newly added report strings (#​13308)
• [BREAKING] group perf audits by details type. change the meaning of an audit whose group is not defined–before no group implied an audit would not be renderered, but now an explicit hidden group is used (#​13241, #​13310)
• [BREAKING] pwa: remove renderScoreGauge, replaced with renderCategoryScore (#​13269)

⛏️👷 Fraggle Rock

Support for auditing user flows (#​11313)

• handle 0 throughput in timespan (#​13323)
• clone default categories to avoid modification (#​13337)
• add timespan support to h2 (#​12814)
• report: remove smooth scrolling (#​13317)
• report: network throttling settings (#​13305)
• report: use filmstrip thumbnail in navigation (#​13283)
• report: fix report anchors (#​13233)
• report: full page screenshot renderer (#​13276)
• report: category tooltip highest impact (#​13230)
• report: import lhr strings (#​13215)
• report: i18n formatter (#​13190)
• report: mock styles (#​13220)

Deps

• bump lighthouse-plugin-publisher-ads (#​13339)
• deps: update chrome-launcher to 0.15.0 (#​13353)

Clients

• devtools: only use locales that have locale files to download (#​13214)
• psi: retire prepareLabData, reuse standard report rendering (#​13229)

I18n

• import (#​13360)
• add better support for the default locale in bundles (#​13211)

Tests

• eslint: add export rule (#​13282)
• longer timeout for installability errors check (#​13297)
• ignore .tmp directory in jest modules (#​13285)
• add cdt folders to devtools test cache buster (#​13268)
• update devtools default branch to 'main' (#​13266)
• ci tests should include all files (#​13235)
• report: throw on axe error (#​13234)
• flow: puppeteer test (#​13281)

Misc

• publish: include the report bundle in npm package (#​13349)
• build: create inline-fs rollup plugin to replace brfs (#​13232, #​13240, #​13248, #​13272, #​13275, #​13278, #​13280)
• build: use rollup to build lighthouse-core bundles (#​12771)
• build: call close method on rollup builds (#​13307)
• build: use prepack script to build report (#​13261)
• build: do not assign runBundledLighthouse in devtools bundle (#​13311)
• build: use cross platform sed for devtools script (#​13242)
• preserve error stack when using promise timeout (#​13333)
• support old devtools in yarn run-devtools (#​13284)
• add report bundles to nightly build (#​13222)
• rename lighthouse-treemap to treemap (#​13246)
• rename lighthouse-viewer to viewer (#​13247)
• simplify release process, run package-test in CI (#​13212)
• add os to bug report template (#​13245)
• proto: add throttling and throttling_method (#​13309)
• revert missing bundle tests (#​13289)
• fix typo (#​13224)

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

npm notice 
npm notice New patch version of npm available! 8.1.0 -> 8.1.3
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.1.3>
npm notice Run `npm install -g [email protected]` to update!
npm notice 

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/dgiot-dashboard/dgiot-dashboard/9xMLvpgh4kXqsFZ2i8pSaPQa6qMj
✅ Preview: https://dgiot-dashboard-git-renovate-lighthouse-9x-dgiot-dashboard.vercel.app

[pull-checklist]

Pull Checklist Limit Reached

We're sorry you've reached your plans limit of 10 Protected Pull Requests per month.

If you find Pull Checklist valuable and would like to upgrade your plan please click here otherwise your limit will reset in 13 days.

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[renovate]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 9.x releases. However, if you upgrade to 9.x manually then Renovate will reenable minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.