[7.17] Upgrade micromatch from v3.1.10 to v4.0.5 (#139187)

[watson]

Backport

This will backport the following commits from main to 7.17:

• Upgrade micromatch from v3.1.10 to v4.0.5 (#139187)

Questions ?

Please refer to the Backport tool documentation

[watson]

@elasticmachine merge upstream

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: aafa7e4
• Interpreting CI Failures
• Storybooks Preview

Failed CI Steps

• Linting

Metrics [docs]

✅ unchanged

History

• 💔 Build #68549 failed c8637a3
• 💔 Build #66676 failed 0c5848c

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[watson]

@spalger I've been puzzled by the linting errors on this PR for a while and suddenly realize that it might be related to #136911 which you created in main not that long ago:

They all seem to be the same:

'@kbn/eslint/no-restricted-paths' rule is disabled but never reported  eslint-comments/no-unused-disable

I'm not sure why this PR suddenly triggers those?!? Maybe the micromatch library is used by eslint and there's a bug in eslint in 7.17 that means it has to use an older version of micromatch? 🤷

In any case... with your knowledge of this eslint rule, do you think it would be safe to simply remove these no-unused-disable lines from the code in 7.17 in this PR?

[spalger]

That wouldn't shock me @watson, @kbn/eslint/no-restricted-paths is implemented in the repository and uses micromatch: https://github.com/elastic/kibana/blob/7.17/packages/kbn-eslint-plugin-eslint/rules/no_restricted_paths.js#L31

Unfortunately I'm unable to bootstrap 7.17 locally or I'd help debug this.

[watson]

We have decided not to complete this backport due to the difficulty in getting the tests to pass (see above comments).