chore(deps): bump chart.js from 2.9.4 to 4.3.0

[dependabot]

Bumps chart.js from 2.9.4 to 4.3.0.

Release notes

Sourced from chart.js's releases.

v4.3.0

Essential Links

• npm
• Migration guide
• Docs
• API
• Samples

• #11257 Bump to 4.3.0
• #11217 Enable applying of gradients and pattern on line segments
• #11134 Use custom scale defaults and dataset axis ID options to determine the axis
• #11061 fix RTL tooltip colorBox placement

Enhancements

• #11055 Enable point labels hiding when overlapped
• #11180 Border is counted as part of ArcElement
• #11121 refactor: rewrite config helpers to ts
• #11100 refactor: rewrite canvas helpers to ts
• #11127 Add borderDash options to arc element

Bugs Fixed

• #11238 Check for isNaN before building number formatter options
• #11116 Fix: don't generate ticks > max if max is specified

Types

• #11121 refactor: rewrite config helpers to ts
• #11100 refactor: rewrite canvas helpers to ts
• #11143 Docs: fix tooltip model doc.

Documentation

• #11241 Add redirect for old V3 migration guides in release notes
• #11244 Fix documentation about how to manage own custom plugin for types
• #11220 docs: Fix a few typos
• #11154 Update tooltip.md

Development

• #11240 Add version specific urls to release template
• #11212 Update size limits
• #11209 chore: change pnpm version in engines field to be able to use 8.x.x
• #11174 Add colors plugin to size limit
• #11165 Disable canvas acceleration in Firefox 110 in test cases
• #11145 Simplify _arrayUnique
• #11135 Change labelColors to labelColor in tooltip drawColorBox method.

... (truncated)

Commits

• 83ba8fd Bump to 4.3.0 (#11257)
• eff39c0 Enable point labels hiding when overlapped (#11055)
• ee7e928 Enable applying of gradients and pattern on line segments (#11217)
• aec1c6d Add redirect for old V3 migration guides in release notes (#11241)
• 69996ab Fix documentation about how to manage own custom plugin for types (#11244)
• a3ccf68 Fix documentation about how to manage own custom plugin for types (#11244)
• cc1fcb0 Add version specific urls to release template (#11240)
• 5ee0ff1 Border is counted as part of ArcElement (#11180)
• b16f32a Check for isNaN before building number formatter options (#11238)
• b34e273 docs: Fix a few typos (#11220)
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

_{Mention [stepsize] in a comment if you'd like to report some technical debt. See examples here.}

[dependabot]

The following labels could not be found: version:3.1.x.

[aviator-app]

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes.
Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This pull request is currently open (not queued).

How to merge

To merge this PR, comment /aviator merge or add the mergequeue label.

[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: 2

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 detected.
• 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.