#### What type of PR is this?
/area ui
/kind improvement
/milestone 2.13.x
#### What this PR does / why we need it:
升级 FormKit 的依赖版本至 1.5.x
Please see https://formkit.com/changelog#_150
#### Does this PR introduce a user-facing change?
```release-note
升级 FormKit 的依赖版本至 1.5.x
```
#### What type of PR is this?
/kind improvement
/area console
/area editor
/milestone 2.13.x
#### What this PR does / why we need it:
重构默认编辑器视频组件。使其支持上传、取消上传、从附件库选择、替换等功能。
#### How to test it?
直接拖动、复制或选择文件上传一个视频，查看是否显示上传进度条，取消、重试功能是否正常
#### Which issue(s) this PR fixes:
Fixes#5240
#### Does this PR introduce a user-facing change?
```release-note
重构编辑器视频组件的上传逻辑，增加选择文件上传、上传进度条、取消、重试等机制。
```
#### What type of PR is this?
/kind feature
/kind improvement
/area core
/area console
/kind api-change
#### What this PR does / why we need it:
增加对用户注册时必须验证邮箱的支持
#### Which issue(s) this PR fixes:
Fixes#5016
#### Special notes for your reviewer:
`regRequireVerifyEmail` 为 `false` 时与现在的注册行为一致
为 `true` 时注册页显示验证码校验相关，注册成功后 `UserSpec.emailVerified` 即为 `true`
没有判断邮件通知是否开启，与现有的邮箱验证一致，如未开启则收不到邮件
#### Does this PR introduce a user-facing change?
```release-note
增加对用户注册时必须验证邮箱的支持
```
#### What type of PR is this?
/area ui
/kind improvement
/milestone 2.13.x
#### What this PR does / why we need it:
升级 Axios 依赖版本至 1.6.x
#### Does this PR introduce a user-facing change?
```release-note
升级 Axios 依赖版本至 1.6.x
```
#### What type of PR is this?
/area ui
/kind bug
/milestone 2.13.x
#### What this PR does / why we need it:
修复 Console 中用户头像无法正确获取的问题。
#### Which issue(s) this PR fixes:
Fixes#5368
#### Special notes for your reviewer:
测试方式：
1. 创建若干用户，并为部分用户设置不同的头像。
2. 分别进入不同用户的个人资料页面，观察头像是否符合预期。
#### Does this PR introduce a user-facing change?
```release-note
修复 Console 中用户头像无法正确获取的问题。
```
#### What type of PR is this?
/kind improvement
#### What this PR does / why we need it:
Correct some simplified Chinese characters that were not replaced in the yaml file of traditional Chinese.
#### Which issue(s) this PR fixes:
Fixes#3672
#### Special notes for your reviewer:
I have read the CONTRIBUTING file, but I'm not familiar with PR operations. If there's anything I can do to improve it, please let me know.
> By the way, the [contribution guidelines](https://github.com/halo-dev/halo/blob/master/CONTRIBUTING.md) provided in the PR template and README still use `master` as the main branch, which may cause some confusion for new contributors.
#### Does this PR introduce a user-facing change?
```release-note
NONE
```
Ryan Wang