[PP-upstream] Update stylelint(-config-standard) to latest versions (major bump)

So the current state of the MR uses stylelint-junit-formatter.
I also opened https://gitlab.com/leon0399/stylelint-formatter-gitlab/-/issues/3 to try and get stylelint-formatter-gitlab working with stylelint 16 and upwards.

Putting this on NR the get some input on:
- if we want to try and get this into 10.2.0
- if so, are we prepared to (temporarily) fallback to using stylelint-junit-formatter and going back to test-errors instead of codequality.

The rules being removed does prettier automatically catch those now?

The rules being removed does prettier automatically catch those now?

Not quite, but good question.

- stylelint has loads of rules, but enables none of them by default.
- stylelint-config-standard enables a bunch of them with some community-defined, sane defaults

Drupal uses a lot of those stylelint-config-standard rules, but overrules some of them with other defaults, and disables others.

The latter one is of interest here. When there's a "[rule-name]": null defined in core/.stylelintrc.json, it _should_ mean stylelint-config-standard-enabled rule, Drupal turns it off. (More on the _should_ below).

The rules that are removed in this issue (function-whitespace-after and max-line-length), were both defined as null, so were turned off in Drupal, so no need for replacement.

Now to the _should_: Turns out during all updates of stylelint and stylelint-config-standard we didn't pay much attention to rules that were dropped at some point from stylelint-config-standard but still being turned off in our core/.stylelintrc.json.
Turning things off that aren't on in the first place is just silly.

Opened [#] to get core/.stylelintrc.json, stylelint and stylelint-config-standard back into sync.

Thanks for explaining!

Thank you for explaining the changes in #10.

As this breaks our current CI integration because stylelint-formatter-gitlab is not yet compatible, I think we should hold off on committing this for a while - there are no pressing changes here and to me this can wait until 10.3.