fix(deps): update dependency antd to ^5.2.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
antd (source)	^5.2.2 -> ^5.2.3

---

Release Notes

ant-design/ant-design

v5.2.3

Compare Source

• 🐞 Fix for setting percent and success.percent at the same time for Progress, the progress text does not change as percent changes. #​40922
• 🐞 Fixed Image preview icon was misaligned.#​40911
• 🐞 Fix ConfigProvider validation message template override Form configure template sometime. #​40533 @​Wxh16144
• 🐞 Fixed Confirm Modal onOk event could be triggered twice when close. #​40719 @​Rafael-Martins
• 🛠 Rewrote the useLocale method and exposed localeCode to the public. #​40884 @​li-jia-nan
• 🐞 Fixed Segmented component items were unresponsive to mouse events. #​40894 @​MadCcc
• 🛠 Refactored: replaced the LocaleReceiver component with useLocale and removed the LocaleReceiver component. #​40870 @​li-jia-nan
• 🐞 Fixed getPopupContainer property injected by ConfigProvider did not work. #​40871 @​RedJue
• 🐞 Fixed where Descriptions did not accept data-_ and aria-_ attributes. #​40859 @​goveo
• 🛠 Changed the Separator's DOM element from span to li. #​40867 @​heiyu4585
• 🐞 Fix token of Layout.colorBgHeader not work when single use Layout.Header directly. #​40933
• 💄 Changed the component's focus outline to the default 4px.#​40839 @​MadCcc
• 🐞 Fixed the Badge color was displayed abnormally. #​40848 @​kiner-tang
• 🐞 Fixed an issue with the Timeline item's className. #​40835 @​Yuiai01
• 💄 Fixed the interaction style of the Rate component in the disabled state.#​40836 @​Yuiai01
• 🇮🇷 Added Iranian localization. #​40895 @​majidsadr

---

• 🐞 修复 Progress 同时设置 percent 和 success.percent 时，进度文本不会随着 percent 改变而改变。#​40922
• 🐞 修复 Image 预览图标不对齐的问题。#​40911
• 🐞 修复 ConfigProvider 组件表单校验消息生效顺序。#​40533 @​Wxh16144
• 🐞 修复 Confirm Modal onOk 可能触发两次的问题。#​40719 @​Rafael-Martins
• 🛠 重写 useLocale 方法，对外暴露 localeCode。#​40884 @​li-jia-nan
• 🐞 修复 Segemented 组件子项不响应鼠标事件的问题。#​40894 @​MadCcc
• 🛠 重构：使用 useLocale 替换 LocaleReceiver 组件，并删除 LocaleReceiver 组件。#​40870 @​li-jia-nan
• 🐞 修复 ConfigProvider 注入的 getPopupContainer 属性 不生效的问题。#​40871 @​RedJue
• 🐞 修复 Descriptions 不接受 data-* 和 aria-* 等属性的问题。#​40859 @​goveo
• 🛠 修改 Separator 的 dom 由 span 改为 li。#​40867 @​heiyu4585
• 💄 修改组件聚焦下的 outline 为默认 4px。#​40839 @​MadCcc
• 🐞 修复 Layout.Header 单独使用时，Layout.colorBgHeader token 配置不生效的问题。#​40933
• 🐞 修复 Badge 颜色显示异常问题。#​40848 @​kiner-tang
• 🐞 修复 Timeline 的子项的 className 错误。#​40835 @​Yuiai01
• 💄 修复 Rate 在禁用状态下的交互样式。#​40836 @​Yuiai01
• 🇮🇷 增加了伊朗本地化。#​40895 @​majidsadr

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[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
.lock : +0 -0

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.