update to browserslist 4.28.1

[tonypconway]

Goals

1. Provide safeguards against the warnings that old versions of baseline-browser-mapping produces

Non-Goals

1. Make any other changes to the browserslist config

Background

Over the last week a lot of users experienced issues as a result of next.js' pre-compilation of browserslist triggering console warnings from the baseline-browser-mapping module. See web-platform-dx/baseline-browser-mapping#105 for the full context.

@lukesandberg 's previous PR #86625 solved this issue in a temporary manner by bumping browserslist to a more recent version and updating to at least [email protected], but that uses the same warning mechanism from the older version and will start to break workflows again in the next few weeks.

Updating to browserslist 4.28.1 will update baseline-browser-mapping to 2.9.0 which has new mechanisms that only warn users that are actually using baseline... queries in their config and only warns them if their old data is going to cause problems in the immediate future. It also adds suppression mechanisms. It's a win win!

Proposal

Repeat whatever you did in #86625 using the most recent versions of browserslist and baseline-browser-mapping.