build(deps): bump github.com/clipperhouse/displaywidth from 0.3.1 to 0.6.0

[dependabot]

Bumps github.com/clipperhouse/displaywidth from 0.3.1 to 0.6.0.

Release notes

Sourced from github.com/clipperhouse/displaywidth's releases.

v0.6.0

What's Changed

• New graphemes iterator & ASCII fast paths by @​clipperhouse in clipperhouse/displaywidth#10

Full Changelog: clipperhouse/displaywidth@v0.5.0...v0.6.0

v0.5.0

This release adopts Unicode 16 and emoji presentation standards per Unicode TR51. Internal updates simplify the properties and trie lookups.

What's Changed

• Emoji presentation and Unicode 16: clipperhouse/displaywidth#7
• Fewer properties, better performance: clipperhouse/displaywidth#8
• Improve VS15 handling: clipperhouse/displaywidth#9

Full Changelog: clipperhouse/displaywidth@v0.4.1...v0.5.0

Changelog

Sourced from github.com/clipperhouse/displaywidth's changelog.

[0.6.0]

Compare

Added

• New StringGraphemes and BytesGraphemes methods, for iterating over the widths of grapheme clusters.

Changed

• Added ASCII fast paths

[0.5.0]

Compare

Added

• Unicode 16 support
• Improved emoji presentation handling per Unicode TR51

Changed

• Corrected VS15 (U+FE0E) handling: now preserves base character width (no-op) per Unicode TR51
• Performance optimizations: reduced property lookups

Fixed

• VS15 variation selector now correctly preserves base character width instead of forcing width 1

[0.4.1]

Compare

Changed

• Updated uax29 dependency
• Improved flag handling

[0.4.0]

Compare

Added

• Support for variation selectors (VS15, VS16) and regional indicator pairs (flags)

Commits

• 0931921 Changlog for v0.6.0
• 3ae9c02 Benchmarks
• 9df5955 New graphemes iterator & ASCII fast paths (#10)
• 9555d41 Create CHANGELOG.md
• 441ce50 Correct VS15 handling for emojis (#9)
• 1a215eb Fewer props (#8)
• e663c23 Emoji presentation and Unicode 16 (#7)
• 9c98084 Update uax29
• 1983f73 More compatibility analysis
• b9a3582 compat notes
• Additional commits viewable in compare view

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)

[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 ivanvc 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

[k8s-ci-robot]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.