[Snyk] Security upgrade axios from 0.21.1 to 0.21.3

[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
	768/1000 Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5	Regular Expression Denial of Service (ReDoS) SNYK-JS-AXIOS-1579269	No	Proof of Concept

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

Commit messages

Package name: axios

The new version differs by 41 commits.

• e367be5 [Releasing] 0.21.3
• 83ae383 Correctly add response interceptors to interceptor chain (ES terms options are not ideal grafana/grafana#4013)
• c0c8761 [Updating] changelog to include links to issues and contributors
• 619bb46 [Releasing] v0.21.2
• 82c9455 Create SECURITY.md (Opentsdb 2.2 filters support without modifying current dashboards grafana/grafana#3981)
• 5b45711 Security fix for ReDoS (Bug: Hide "or login with" when no oauth options are configured  grafana/grafana#3980)
• 5bc9ea2 Update ECOSYSTEM.md (FR: Enhance ES query editor grafana/grafana#3817)
• e72813a Fixing README.md (Forward Slash "/" not searchable for Elastiscsearch query grafana/grafana#3818)
• e10a027 Fix README typo under Request Config (WIP: Reuse panels across dashboards grafana/grafana#3825)
• e091491 Update README.md (Snapshot created with API requires login grafana/grafana#3936)
• b42fbad Removed un-needed bracket
• 520c8dc Updating CI status badge (FR: User removal from Org and Global users grafana/grafana#3953)
• 4fbeecb Adding CI on Github Actions. (Auto refresh hides backend error grafana/grafana#3938)
• e9965bf Fixing the sauce labs tests (the position of the points on the lines is error sometimes grafana/grafana#3813)
• dbc634c Remove charset in tests (allow saving changes to appModel made by configView directive grafana/grafana#3807)
• 3958e9f Add explanation of cancel token (add export to csv in table panel grafana/grafana#3803)
• 69949a6 Adding custom return type support to interceptor (Possibility to hide table header grafana/grafana#3783)
• 49509f6 Create FUNDING.yml (Grafana Annotations are not working fine grafana/grafana#3796)
• 199c8aa Adding parseInt to config.timeout (Align The requested period with Interval if Interval templating is used grafana/grafana#3781)
• 94fc4ea Adding isAxiosError typeguard documentation (Suggestions to improve the user experience for the ES database grafana/grafana#3767)
• 0ece97c Fixing quadratic runtime when setting a maxContentLength (UX: Fix light theme button color grafana/grafana#3738)
• a18a0ec Updating `lib/core/README.md` about Dispatching requests (Elasticsearch: Support nested property names in field auto completion  grafana/grafana#3772)
• 59fa614 [Updated] follow-redirects to the latest version (fix(login): fix vulnerbility for timing attacks grafana/grafana#3771)
• 7821ed2 Feat/json improvements (influxdb : GROUP BY time(auto) too granular. grafana/grafana#3763)

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.