[Snyk] Security upgrade react-dev-utils from 10.2.1 to 11.0.0

[snyk-bot]

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • packages/grafana-toolkit/package.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	586/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 5.3	Regular Expression Denial of Service (ReDoS) SNYK-JS-GLOBPARENT-1016905	Yes	Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: react-dev-utils

The new version differs by 125 commits.

• ed95893 Publish
• 88ca4f6 Prepare 4.0.0 release
• d23d615 Update react dom in error overlay
• 95265c3 Update CHANGELOG
• 523b416 Add link to Open Collective (Add template variables to the annotations tags grafana/grafana#9864)
• af616ab Update CHANGELOG
• 014ca01 Prepare 4.0.0 release
• 2b1161b Pass JSX runtime setting to Babel preset in Jest config (Changing charset in MYSQL DataSource grafana/grafana#9865)
• f2aef41 Prepare 4.0.0 alpha release
• 4bc639c Upgrade to React 17 ([UX]: Make lists/table design & table actions and make confirm delete action smoother  grafana/grafana#9863)
• d61347d Use new JSX setting with TypeScript 4.1.0 ([Feature request]: Release security fixes separately to breaking changes grafana/grafana#9734)
• e63de79 New JSX Transform opt out (Undocumented frontend build requirements grafana/grafana#9861)
• fe785b2 feat: Update all dependencies ([Bug] Custom code editor language definitions not loading from external plugins  grafana/grafana#9857)
• 85ab02b feat: remove unused React imports (Handle built-in variables (such as $timeFilter) in template variables grafana/grafana#9853)
• 329f392 feat: Update ESLint dependencies ((cloudwatch) return empty array for no datapoints grafana/grafana#9856)
• 10fa972 feat(eslint-config-react-app): Add jest & testing-library rules ([Bug] Typo in alert_howto grafana/grafana#8963)
• ed919b1 Make eslint-plugin-jest an optional peerDependency ([feature request]: label and title with Mathematical Expression Using LaTeX grafana/grafana#9670)
• 0a93e32 Fix refreshOverlayInterop module scope error ([Bug] The first condition's operator is "or" will cause "alert" to determine abnormal. grafana/grafana#9805)
• 7965594 Bump resolve-url-loader version (Postgres: sync documentation, add remark about to_timestamp and redshift grafana/grafana#9841)
• b1f8536 Add 3.4.4 to the changelog
• d07b7d0 Replace deprecated eslint-loader with eslint-webpack-plugin (new design for no alerts in alert-list, fixes #9721 grafana/grafana#9751)
• 6f3e32e Upgrade Docusaurus to latest version ([Bug] Cannot use password containing "!" grafana/grafana#9728)
• 1f2d387 fix: resolve new JSX runtime issues (update lib/pq grafana/grafana#9788)
• 6a51dcd Add AVIF image support (dont quote variables for mysql and postgres datasource grafana/grafana#9611)

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.