chore(deps-dev): bump vega from 5.23.0 to 5.33.0 in /apps/web

[dependabot]

Bumps vega from 5.23.0 to 5.33.0.

Release notes

Sourced from vega's releases.

v5.33.0

Changes since v5.32.0

docs

• Add release number to docs for base64 encode/decode (atob, btoa) (via #4023). (Thanks @​hydrosquall!)
• Fix docs for exponential regression (via #4024). (Thanks @​elliot-at-looker!)

v5.32.0

Changes since v5.31.0

vega-expression

• Add base64 string encoder/decoder to vega-expression and vega-interpreter (via #4009). (Thanks @​hydrosquall!)

vega-typings

• Add Typescript Types for vega-loader (via #4000). (Thanks @​hydrosquall!)

docs

• Correct data year citation in dorling-cartogram example (via #4006). (Thanks @​dsmedia!)
• Update typo in vega.timeFloor description (via #4010). (Thanks @​hydrosquall!)
• Add Security Advisory Policy for Vega (via #4008). (Thanks @​hydrosquall!)
• Replace redirect url in expressions.md (via #3996). (Thanks @​dangotbanned!)
• correct queries to query in crossfilter.md (via #4005). (Thanks @​danmarshall!)

v5.31.0

changes since v5.30.0

vega-utils

• use Object.hasOwn instead of Object.prototype.hasOwnProperty (via #3951). (Thanks @​domoritz!)

vega-parser

• Add discrete legend type (via #3957). (Thanks @​hydrosquall!)

vega-functions

• Add sort function to vega-functions (and vega-interpreter) (via #3973). (Thanks @​hydrosquall!)

vega-selections

• Add field predicate types to selectionTest (via #3675). (Thanks @​jonathanzong!)

monorepo

• Replace flights-5k.json external reference (via #3999). (Thanks @​dwootton!)

docs

• Update packed bubble example (via #3955). (Thanks @​PBI-David!)
• Correct typo in production rules documentation (via #3958). (Thanks @​shanebruggeman!)
• Update README.md to fix broken link to current roadmap (via #3979). (Thanks @​cahogan & @​joelostblom!)

v5.30.0

Changes since v5.29.0

vega-functions

... (truncated)

Commits

• 57c2a12 chore: v5.33.0 (#4027)
• 644c971 docs: fix docs for exponential regression (#4024)
• ec92384 Merge commit from fork
• aa03ef9 docs(vega-expression): Add release number to docs for base64 encode/decode (...
• c46889d chore: update vega-cli to v5.32.0 (#4015)
• 2fe2e63 chore: v5.32.0 (#4014)
• 81ed011 chore: remove extra space in test name
• 6026887 fix: correct data year citation in dorling-cartogram example (#4006)
• a3af49e feat: Add base64 string encoder/decoder to vega-expression and `vega-interp...
• cd88cc8 fix(docs): Update typo in vega.timeFloor description (#4010)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by lhermann, a new releaser for vega since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign koksay for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Deploy Preview for apisnoop ready!

Name	Link
🔨 Latest commit	62b68a8
🔍 Latest deploy log	https://app.netlify.com/sites/apisnoop/deploys/67e55d264ff9dc000864f868
😎 Deploy Preview	https://deploy-preview-939--apisnoop.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten