fix(deps): update dependency antd to ^5.6.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
antd (source)	^5.6.2 -> ^5.6.3

---

Release Notes

ant-design/ant-design (antd)

v5.6.3

Compare Source

• BreadCrumb
  • 🐞 Fix BreadCrumb dropdownProps does not working bug. #​43151 @​linxianxi
  • 🛠 Improve BreadCrumb behavior when receiving a null title. #​43099 @​Asanio06
• 🐞 Fix Slider disabled state within Form. #​43142 @​Starpuccino
• 🐞 Fix Form that label offset does not work in vertical mode. #​43155 @​kiner-tang
• 🐞 Fix Table open filter popup throw react ref warning. #​43139
• 🐞 Fix Transfer with rowKey makes item unselectable. #​43115
• 🐞 Fix Space size priority when using with other components #​42752 @​linxianxi
• 🐞 Fix QRCode color in dark mode. #​43162 @​ds1371dani
• 💄 Fix Select option unexpected margin when using with Badge and Tag. #​43097 @​Yuiai01
• TypeScript
  • 🤖 Improve Button target property type definition. #​43129 @​li-jia-nan
  • 🤖 Improve Progress size property type to support percent value. #​43123 @​Ali-ovo
  • 🤖 Improve Slider tooltip type definition. #​43094 @​li-jia-nan

---

• BreadCrumb
  • 🐞 修复 BreadCrumb 传递 dropdownProps 不生效的问题。#​43151 @​linxianxi
  • 🛠 优化 BreadCrumb 处理 title 为 null 时的行为。#​43099 @​Asanio06
• 🐞 修复 Slider 在 Form 内部时的禁用状态。#​43142 @​Starpuccino
• 🐞 修复 Form 标签偏移值在垂直布局中不生效的问题。#​43155 @​kiner-tang
• 🐞 修复 Table 打开筛选面板会报 react ref 错误警告信息。#​43139
• 🐞 修复 Transfer 配置 rowKey 后无法选中的问题。#​43115
• 🐞 修复 Space 与其他组件搭配使用时的 size 优先级#​42752 @​linxianxi
• 🐞 修复 QRCode 在暗黑模式下的颜色。#​43162 @​ds1371dani
• 💄 修复 Select 选项使用 Badge 和 Tag 时底部存在意外边距的问题。#​43097 @​Yuiai01
• TypeScript
  • 🤖 优化 Button 的 target 属性类型定义。#​43129 @​li-jia-nan
  • 🤖 优化 Progress 的 size 属性类型定义以支持百分比值。#​43123 @​Ali-ovo
  • 🤖 优化 Slider tooltip 的类型定义。#​43094 @​li-jia-nan

---

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.