build(deps-dev): bump baseline-browser-mapping from 2.8.9 to 2.9.2

[dependabot]

Bumps baseline-browser-mapping from 2.8.9 to 2.9.2.

Release notes

Sourced from baseline-browser-mapping's releases.

v2.9.2 - fix browser support bug

What's Changed

• Fix browser support bug by @​tonypconway in web-platform-dx/baseline-browser-mapping#111 Full Changelog: web-platform-dx/baseline-browser-mapping@v2.9.1...v2.9.2

v2.9.0 - Reduce frequency of data staleness warnings

This version introduces a number of changes to data staleness warnings in response to #105 , #107 and #109

• Data staleness warnings are now only shown if the getCompatibleVersions() or getAllVersions() functions are called - previously they were shown whenever the module was loaded, which meant many browserslist consumers were seeing the warning despite not targeting Baseline, especially those who were consuming browserslist in a pre-compiled format via next.js.
• Adds new conditions for these warnings to be displayed which should only warn users for whom data freshness is critical:
  • The feature cut off data must be within the last two months, i.e. widelyAvailableOnDate: today + >2 years and 4 months or newly available in a browserslist query.
  • The module data must be more than 2 months old.
• Introduces suppression options for these warning via the options objects and environment variables:
  • Adds a new suppressWarnings boolean to the getCompatibleVersions() and getAllVersions()
  • Respects the existing BROWSERSLIST_IGNORE_OLD_DATA environment variable.
  • Respects a new BASELINE_BROWSER_MAPPING_IGNORE_OLD_DATA environment variable.
• Adds explanatory text to the README for how to avoid such warnings when reproducible builds are a requirement.
• Change warning text to be package manager agnostic and mention the possibility of pre-compiled data.

Commits

• 5972583 Bump version from 2.9.1 to 2.9.2
• 0ab0d6f Fix browser support bug (#111)
• b326475 Patch to 2.9.1 because browser or feature data changed
• 9ee8cbe Browser or feature data changed
• 226fd01 Reduce frequency of data staleness warnings (#108)
• 6d43e5a Updating static site
• 0b0877b Patch to 2.8.32 because browser or feature data changed
• f5de0cc Browser or feature data changed
• 0c1ec94 Bump glob from 10.4.5 to 10.5.0 (#106)
• 9285864 Updating static site
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[patternfly-build]

Preview: https://react-data-view-pr-data-view-566.surge.sh

A11y report: https://react-data-view-pr-data-view-566-a11y.surge.sh