chore: update minimatch to version 9.0.5 and brace-expansion to version 2.0.2

[QuantumExplorer]

Issue being fixed or feature implemented

Updated the minimatch package to version 9.0.5 and the brace-expansion package to version 2.0.2 to ensure compatibility and take advantage of the latest features and bug fixes.

What was done?

• Updated minimatch from version 3.1.2 (and several intermediate versions) to 9.0.5.
• Updated brace-expansion from version 2.0.1 to 2.0.2.
• Removed deprecated versions of minimatch and brace-expansion from the project.

How Has This Been Tested?

Changes were validated through existing unit tests, which cover the functionality dependent on these packages.

Breaking Changes

None

Checklist

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have added ! to the title and described breaking changes in the corresponding section if my code contains any.

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

Summary by CodeRabbit

• Chores
  • Updated internal package dependencies to the latest versions of minimatch and brace-expansion.
  • Added resolutions for brace-expansion (2.0.2) to ensure consistent dependency versions.
  • Removed obsolete packages from the dependency tree for improved package management.

[coderabbitai]

Walkthrough

This update standardizes the version of the minimatch dependency to 9.0.5 and updates brace-expansion to 2.0.2 across the project by modifying the .pnp.cjs and package.json files. The changes are limited to dependency version upgrades and package metadata, with no alterations to code logic or public interfaces.

Changes

File(s)	Change Summary
.pnp.cjs	Upgraded all references of minimatch to 9.0.5, updated brace-expansion to 2.0.2, removed old versions and concat-map.
package.json	Added brace-expansion@2.0.2 to the resolutions section.

Poem

In the warren of code, dependencies hop,
Now minimatch and friends take a unified stop.
No more old versions, just one shiny new,
With brace-expansion updated, the garden feels new.
🐇✨ Hoppity hooray, the package path is clear—
Onward to builds with less to fear!

Suggested labels

cleanup

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3eb03a1 and 4c931e4.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (2)

• .pnp.cjs (8 hunks)
• package.json (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (2)

• package.json
• .pnp.cjs

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Build Docker images (Dashmate helper, dashmate-helper, dashmate-helper) / Build Dashmate helper image
• GitHub Check: Build Docker images (DAPI, dapi, dapi) / Build DAPI image
• GitHub Check: Build JS packages / Build JS

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.