#### What type of PR is this?
/area console
/kind feature
/milestone 2.9.x
#### What this PR does / why we need it:
支持选择已有备份进行恢复。
<img width="1628" alt="image" src="https://github.com/halo-dev/halo/assets/21301288/5e3169f7-a604-4e20-9c4e-f6bc68c58d59">
#### Special notes for your reviewer:
需要测试在恢复界面通过选择已有备份进行恢复的功能是否正常。
#### Does this PR introduce a user-facing change?
```release-note
系统恢复功能支持选择已有备份进行系统恢复。
```
#### What type of PR is this?
/area editor
/area console
#### What this PR does / why we need it:
1. mac: 在编辑器中添加command+s保存文章
2. windows: 在编辑器中添加ctrl+s保存文章
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/4340
#### Does this PR introduce a user-facing change?
```release-note
Console 端支持通过快捷键保存文章
```
#### What type of PR is this?
/area console
/kind improvement
/milestone 2.9.x
#### What this PR does / why we need it:
重构数据列表操作项和显示字段扩展点的类型定义和条件判断：
1. `EntityDropdownItem` 改为 `OperationItem` 以适配不同的场景，最开始仅仅是为了提供给 Entity 组件，但后面发现如主题管理列表并没有使用 Entity 组件，所以定义统一改为 Operation 。
2. 修改 `OperationItem` 和 `EntityFieldItem` 的 `visible` 字段为 `hidden`，方便渲染的时候判断，并方便调用方默认不设置值。
#### Does this PR introduce a user-facing change?
```release-note
None
```
#### What type of PR is this?
/area console
/kind feature
/milestone 2.9.x
#### What this PR does / why we need it:
主题管理列表项的操作按钮支持被插件扩展。
#### Which issue(s) this PR fixes:
Fixes#4522
#### Special notes for your reviewer:
测试已有的操作按钮功能正常即可。
#### Does this PR introduce a user-facing change?
```release-note
Console 主题管理列表项的操作按钮支持被插件扩展。
```
#### What type of PR is this?
/area console
/kind feature
/milestone 2.9.x
#### What this PR does / why we need it:
Halo 在 https://github.com/halo-dev/halo/pull/4452 中为数据列表的操作选项添加了拓展点，用于通过插件扩展操作选项。但忽略了操作选项的组件需要自定义并且自行处理点击事件，这个时候组件应该比较难拿到数据列表项的数据。
此 PR 对此进行优化，在扩展点方法传入了需要的数据。
#### Does this PR introduce a user-facing change?
```release-note
None
```
#### What type of PR is this?
/area console
/kind improvement
/milestone 2.9.x
#### What this PR does / why we need it:
禁用 Dropdown 组件的自动销毁 dom 节点功能，以适配 https://github.com/halo-dev/halo/pull/4452 中拓展操作选项的场景。
#### Does this PR introduce a user-facing change?
```release-note
None
```
#### What type of PR is this?
/area console
/kind bug
/milestone 2.9.x
#### What this PR does / why we need it:
修复可能因为 version 锁的原因导致无法正常切换插件状态，现在改为在调用切换状态接口前，获取一次最新的插件信息，并提供了 retry 的配置，即失败之后重试 3 次。
#### Special notes for your reviewer:
测试能否正常切换插件状态即可。
#### Does this PR introduce a user-facing change?
```release-note
None
```
#### What type of PR is this?
/kind bug
/area console
/milestone 2.9.x
#### What this PR does / why we need it:
解决评论管理中，根据是否已审核状态的筛选无效的问题
#### How to test it?
在评论列表上切换审核状态，查看是否有效。
#### Which issue(s) this PR fixes:
Fixes#4494
#### Does this PR introduce a user-facing change?
```release-note
修复评论管理中审核状态筛选无效的问题
```
#### What type of PR is this?
/kind bug
/area console
/milestone 2.9.x
#### What this PR does / why we need it:
更改自动保存的策略，仅当内容具有缓存时才会执行自动保存。
#### How to test it?
新建/更新一篇文章之后，点击发布，查看是否还存在“文章已保存但未发布” 的提示
#### Which issue(s) this PR fixes:
Fixes#4499
#### Does this PR introduce a user-facing change?
```release-note
修复文章发布后，文章列表显示未发布的问题。
```
#### What type of PR is this?
/area console
/kind feature
/milestone 2.9.x
#### What this PR does / why we need it:
备份列表的操作列表支持被插件扩展。
#### Does this PR introduce a user-facing change?
```release-note
Console 端的备份列表的操作按钮列表支持扩展。
```
#### What type of PR is this?
/area console
/kind improvement
/milestone 2.9.x
#### What this PR does / why we need it:
在 https://github.com/halo-dev/halo/pull/4473 中移除了插件管理的分页功能，但可能会造成列表底部看起来不协调，所以恢复总条数的文字显示。
#### Which issue(s) this PR fixes:
Fixes#4498
#### Does this PR introduce a user-facing change?
```release-note
None
```
#### What type of PR is this?
/area console
/kind cleanup
#### What this PR does / why we need it:
更新 Console 中 package.json 文件的 repository 设置。
#### Does this PR introduce a user-facing change?
```release-note
None
```
#### What type of PR is this?
/kind improvement
#### What this PR does / why we need it:
本 PR 优化了文章、内容编辑时的本地缓存功能，之前内容对于本地缓存的依赖性非常强，因此导致了部分问题，如 #3820 ，本 PR 计划之后本地缓存将仅用于特殊情况下的内容恢复，因此尝试做了如下修改：
1. 当前正在编辑的文章，会在正常模式（切换路由、刷新页面、失去当前窗口焦点、停止编写一定时间均属于正常模式）下进行自动保存后删除本地缓存。
2. 若本地具有缓存，则会在进入编辑页面时，比对一次 content 的 version，若缓存 version 小于线上 version，则抛弃缓存，若一致，则使用缓存。
但经过测试，本 PR 无法解决如下问题：
1. 同时编辑一篇文章时，内容会被覆盖的问题。
2. 对比版本后会抛弃缓存，而实际上应当将本地缓存加入历史版本中。
#### How to test it?
1. 新建一篇文章，编写任意内容，返回文章页查看是否已经具有新的文章，且内容已被保存。
2. 修改一篇文章的内容，然后返回文章页，查看是否不是从缓存中加载。
3. 断网模式下修改一篇文章的内容，然后返回文章页，联网后，再次打开此文章，查看是否显示从缓存中加载。
4. 断网模式下修改一篇文章的内容，然后返回文章页。在另一个浏览器或页面修改此文章并保存后，回到断网页面联网后，查看是否更新为最新内容。
#### Which issue(s) this PR fixes:
Fixes#3820Fixes#4223
#### Does this PR introduce a user-facing change?
```release-note
减少内容编辑对本地缓存依赖，支持内容自动保存至服务端。
```
#### What type of PR is this?
/area console
/kind improvement
/milestone 2.9.x
#### What this PR does / why we need it:
移除插件管理列表的分页功能，默认列表出所有安装的插件。
#### Which issue(s) this PR fixes:
Fixes#4469
#### Does this PR introduce a user-facing change?
```release-note
移除 Console 端插件管理列表的分页功能，默认列表出所有安装的插件。
```
#### What type of PR is this?
/area console
/kind bug
/milestone 2.9.x
#### What this PR does / why we need it:
修复因为初始化数据异常导致没有记录初始化状态的问题，这个问题可能会导致失败之后无法再让系统正常访问。
#### Does this PR introduce a user-facing change?
```release-note
None
```
#### What type of PR is this?
/kind feature
/area core
/milestone 2.9.x
#### What this PR does / why we need it:
Currently, we only support restoring by uploading backup file. Downloading and uploading larger backup files can be cumbersome for users.
This PR supports restoring with downloadable URL or backup name as well.
#### Special notes for your reviewer:
```bash
# Replace ${BACKUP_NAME} by yourself.
curl -u admin:admin 'http://localhost:8090/apis/api.console.migration.halo.run/v1alpha1/restorations' \
-H 'Content-Type: multipart/form-data; boundary=----WebKitFormBoundary3Al7pC6AbBNfB1js' \
--data-raw $'------WebKitFormBoundary3Al7pC6AbBNfB1js\r\nContent-Disposition: form-data; name="backupName"\r\n\r\n${BACKUP_NAME}\r\n------WebKitFormBoundary3Al7pC6AbBNfB1js--\r\n'
```
```bash
# Replace ${DOWNLOAD_LINK} by yourself.
curl -u admin:admin 'http://localhost:8090/apis/api.console.migration.halo.run/v1alpha1/restorations' \
-H 'Content-Type: multipart/form-data; boundary=----WebKitFormBoundarytv6cqgmANkCpSuZm' \
--data-raw $'------WebKitFormBoundarytv6cqgmANkCpSuZm\r\nContent-Disposition: form-data; name="downloadUrl"\r\n\r\n${DOWNLOAD_LINK}\r\n------WebKitFormBoundarytv6cqgmANkCpSuZm--\r\n'
```
#### Does this PR introduce a user-facing change?
```release-note
新增提供下载链接或者备份名进行系统恢复的功能。
```
#### What type of PR is this?
/area console
/kind cleanup
/milestone 2.9.x
#### What this PR does / why we need it:
升级 Console 端上传组件（Uppy）相关依赖的版本。
#### Does this PR introduce a user-facing change?
```release-note
升级 Console 端上传组件（Uppy）相关依赖的版本。
```
#### What type of PR is this?
/kind bug
/area console
/kind improvement
#### What this PR does / why we need it:
当用户对头像进行删除或修改时，文章页面和用户页面的头像会出现显示错误。
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/4408
Fixes https://github.com/halo-dev/halo/issues/4352
#### Special notes for your reviewer:
#### Does this PR introduce a user-facing change?
```release-note
修复 Console 端头像组件的图片更新问题
```
<!-- Thanks for sending a pull request! Here are some tips for you:
1. 如果这是你的第一次，请阅读我们的贡献指南：<https://github.com/halo-dev/halo/blob/master/CONTRIBUTING.md>。
1. If this is your first time, please read our contributor guidelines: <https://github.com/halo-dev/halo/blob/master/CONTRIBUTING.md>.
2. 请根据你解决问题的类型为 Pull Request 添加合适的标签。
2. Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request.
3. 请确保你已经添加并运行了适当的测试。
3. Ensure you have added or ran the appropriate tests for your PR.
-->
#### What type of PR is this?
/kind bug
/area console
<!--
添加其中一个类别：
Add one of the following kinds:
/kind bug
/kind cleanup
/kind documentation
/kind feature
/kind improvement
适当添加其中一个或多个类别（可选）：
Optionally add one or more of the following kinds if applicable:
/kind api-change
/kind deprecation
/kind failing-test
/kind flake
/kind regression
-->
#### What this PR does / why we need it:
文章标题过长时，面板“最近文章”会存在日期显示不完整
#### Which issue(s) this PR fixes:
<!--
PR 合并时自动关闭 issue。
Automatically closes linked issue when PR is merged.
用法：`Fixes #<issue 号>`，或者 `Fixes (粘贴 issue 完整链接)`
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->
Fixes https://github.com/halo-dev/halo/issues/4304
#### Special notes for your reviewer:
目前我的解决方案是将Entity加上一个flex-wrap，这样可以保证日期显示完整，但是这可能导致上下文章的布局结构不统一。不知是否可以采纳。
#### Does this PR introduce a user-facing change?
<!--
如果当前 Pull Request 的修改不会造成用户侧的任何变更，在 `release-note` 代码块儿中填写 `NONE`。
否则请填写用户侧能够理解的 Release Note。如果当前 Pull Request 包含破坏性更新（Break Change），
Release Note 需要以 `action required` 开头。
If no, just write "NONE" in the release-note block below.
If yes, a release note is required:
Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required".
-->
```release-note
用户在仪表板页面为`最近文章`设置的宽度不够时，可以显示创建日期
```
<!-- Thanks for sending a pull request! Here are some tips for you:
1. 如果这是你的第一次，请阅读我们的贡献指南：<https://github.com/halo-dev/halo/blob/master/CONTRIBUTING.md>。
1. If this is your first time, please read our contributor guidelines: <https://github.com/halo-dev/halo/blob/master/CONTRIBUTING.md>.
2. 请根据你解决问题的类型为 Pull Request 添加合适的标签。
2. Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request.
3. 请确保你已经添加并运行了适当的测试。
3. Ensure you have added or ran the appropriate tests for your PR.
-->
#### What type of PR is this?
/kind feature
/area console
<!--
添加其中一个类别：
Add one of the following kinds:
/kind bug
/kind cleanup
/kind documentation
/kind feature
/kind improvement
适当添加其中一个或多个类别（可选）：
Optionally add one or more of the following kinds if applicable:
/kind api-change
/kind deprecation
/kind failing-test
/kind flake
/kind regression
-->
#### What this PR does / why we need it:
将 AttachmentFileTypeIcon 在 Console 全局进行注册，以在插件中复用此组件。
#### Which issue(s) this PR fixes:
<!--
PR 合并时自动关闭 issue。
Automatically closes linked issue when PR is merged.
用法：`Fixes #<issue 号>`，或者 `Fixes (粘贴 issue 完整链接)`
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->
Fixes https://github.com/halo-dev/halo/issues/4413
#### Special notes for your reviewer:
我把组件放到 `@/components` 里了，不合适我改回去
#### Does this PR introduce a user-facing change?
<!--
如果当前 Pull Request 的修改不会造成用户侧的任何变更，在 `release-note` 代码块儿中填写 `NONE`。
否则请填写用户侧能够理解的 Release Note。如果当前 Pull Request 包含破坏性更新（Break Change），
Release Note 需要以 `action required` 开头。
If no, just write "NONE" in the release-note block below.
If yes, a release note is required:
Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required".
-->
```release-note
None
```
#### What type of PR is this?
/area console
/kind improvement
/milestone 2.9.x
#### What this PR does / why we need it:
移除启动/停止插件的确认弹框。
#### Which issue(s) this PR fixes:
Fixes#4471
#### Special notes for your reviewer:
测试启动和停止插件是否正常工作即可。
#### Does this PR introduce a user-facing change?
```release-note
移除 Console 端启动/停止插件的确认弹框。
```
#### What type of PR is this?
/area console
/kind feature
/milestone 2.9.x
#### What this PR does / why we need it:
Console 端的 Tabs 组件支持通过鼠标滚动选项卡。
#### Which issue(s) this PR fixes:
Fixes#4353
#### Special notes for your reviewer:
None
#### Does this PR introduce a user-facing change?
```release-note
Console 端的 Tabs 组件支持通过鼠标滚动选项卡。
```
#### What type of PR is this?
/kind feature
/milestone 2.3.x
/area core
#### What this PR does / why we need it:
提供 `/apis/api.console.halo.run/v1alpha1/plugins/bundle.js` 来获取已启用插件的捆绑后的 main.js 和 style.css 文件
#### Which issue(s) this PR fixes:
Fixes#3442
#### Does this PR introduce a user-facing change?
```release-note
优化已启用插件 jsbundle 文件的加载方式
```
#### What type of PR is this?
/kind bug
/area console
/milestone 2.9.x
#### What this PR does / why we need it:
Console 评论列表中，使用用户名查询时携带 kind
#### How to test it?
在 Console 端评论列表，选中右上角评论者，进行选择。
#### Which issue(s) this PR fixes:
Fixes#4465
#### Does this PR introduce a user-facing change?
```release-note
解决评论列表根据评论者条件筛选时为空的问题
```
#### What type of PR is this?
/kind improvement
/kind console
#### What this PR does / why we need it:
修改附件显示模式后，保存状态
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/4476
#### Does this PR introduce a user-facing change?
```release-note
Console 端附件管理的显示模式支持缓存到浏览器。
```
#### What type of PR is this?
/area console
/kind improvement
/milestone 2.9.x
#### What this PR does / why we need it:
优化插件升级相关代码，解决插件管理列表的潜在性能问题。
#### Which issue(s) this PR fixes:
Fixes#4409
#### Special notes for your reviewer:
需要测试插件安装和升级功能
#### Does this PR introduce a user-facing change?
```release-note
优化 Console 端插件管理列表的性能
```
A function to debounce editor updates was added to the DefaultEditor.vue component. This change was necessary to prevent excessive event executions. Now, 'update:raw', 'update:content', and 'update' events will be emitted 250ms after the last update, reducing the number of redundant operations and increasing the editor's performance.
<!-- Thanks for sending a pull request! Here are some tips for you:
1. 如果这是你的第一次，请阅读我们的贡献指南：<https://github.com/halo-dev/halo/blob/master/CONTRIBUTING.md>。
1. If this is your first time, please read our contributor guidelines: <https://github.com/halo-dev/halo/blob/master/CONTRIBUTING.md>.
2. 请根据你解决问题的类型为 Pull Request 添加合适的标签。
2. Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request.
3. 请确保你已经添加并运行了适当的测试。
3. Ensure you have added or ran the appropriate tests for your PR.
-->
#### What type of PR is this?
/kind improvement
<!--
添加其中一个类别：
Add one of the following kinds:
/kind bug
/kind cleanup
/kind documentation
/kind feature
/kind improvement
适当添加其中一个或多个类别（可选）：
Optionally add one or more of the following kinds if applicable:
/kind api-change
/kind deprecation
/kind failing-test
/kind flake
/kind regression
-->
#### What this PR does / why we need it:
目前默认编辑器在文章内容过多时，会出现输入延迟。
#### Which issue(s) this PR fixes:
<!--
PR 合并时自动关闭 issue。
Automatically closes linked issue when PR is merged.
用法：`Fixes #<issue 号>`，或者 `Fixes (粘贴 issue 完整链接)`
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->
Fixes#4389
#### Special notes for your reviewer:
#### Does this PR introduce a user-facing change?
<!--
如果当前 Pull Request 的修改不会造成用户侧的任何变更，在 `release-note` 代码块儿中填写 `NONE`。
否则请填写用户侧能够理解的 Release Note。如果当前 Pull Request 包含破坏性更新（Break Change），
Release Note 需要以 `action required` 开头。
If no, just write "NONE" in the release-note block below.
If yes, a release note is required:
Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required".
-->
```release-note
增强默认编辑器在文章内容过大时的性能。
```
#### What type of PR is this?
/area console
/kind feature
/milestone 2.9.x
#### What this PR does / why we need it:
为 FormKit 的 password 类型输入框添加统一的显示/隐藏明文按钮。
<img width="541" alt="image" src="https://github.com/halo-dev/halo/assets/21301288/2947cef2-258c-434d-9268-c8b5ad26a9f7">
#### Which issue(s) this PR fixes:
Fixes#4382
#### Special notes for your reviewer:
测试密码输入框的显示隐藏明文按钮是否可以正常使用即可。
#### Does this PR introduce a user-facing change?
```release-note
为 FormKit 的 password 类型输入框添加统一的显示/隐藏明文按钮。
```
#### What type of PR is this?
/area console
/kind improvement
/milestone 2.9.x
#### What this PR does / why we need it:
升级 Vue 至 3.3 以及相关的依赖。
see https://blog.vuejs.org/posts/vue-3-3
#### Which issue(s) this PR fixes:
Fixes#4425
#### Does this PR introduce a user-facing change?
```release-note
升级 Vue 至 3.3 以及相关的依赖。
```
#### What type of PR is this?
/kind bug
/area console
/milestone 2.9.x
#### What this PR does / why we need it:
原先使用 uppy 上传文件时抛出异常时，处理了 Halo 系统内部异常，但并未处理外部抛出的异常，例如反向代理等，因而会导致上传文件时卡在 0% 或者 100%。
更改之后当上传抛出异常时，首先会尝试将异常信息转换为 JSON，如果转换失败，则代表为外部异常，此时会抛出异常信息，异常信息格式为 `status: statusText`。
<img width="1045" alt="image" src="https://github.com/halo-dev/halo/assets/31335418/228a73aa-b22e-40f9-b69d-3180e2f78032">
#### How to test it?
在 Halo 上传接口前增加一层反向代理，并设置最大允许文件值，之后上传超过其值的文件进行尝试，若能够成功抛出异常即可。
#### Which issue(s) this PR fixes:
Fixes#4359
#### Does this PR introduce a user-facing change?
```release-note
修复上传文件时由于外部异常而导致进度条不变的问题
```
#### What type of PR is this?
/kind bug
#### What this PR does / why we need it:
对 console 跳转链接进行编码，用于解决跳转链接中如果携带非标准字符而导致的报错
#### How to test it?
本地开发环境：重定向地址无误且进行了 uri 编码即可。
生产环境：
在 console 后端未登录时，前往应用市场输入网站地址进行安装，之后进行登录，查看是否能够正确跳转。
#### Which issue(s) this PR fixes:
Fixes#4351
#### 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:
由于后端 annotation 的值可以为空，而前端则规定 annotation 值为必填项，因此去除前端必填属性。
#### Which issue(s) this PR fixes:
Fixes#4279
#### Does this PR introduce a user-facing change?
```release-note
将元数据值更改为非必填
```
#### What type of PR is this?
/area console
/kind cleanup
/milestone 2.9.x
#### What this PR does / why we need it:
升级 FormKit 的依赖至 0.17.5
see https://formkit.com/changelog
#### Does this PR introduce a user-facing change?
```release-note
升级 FormKit 的依赖至 0.17.5
```
* refactor: improve the system initialization process
* Sync api-client
Signed-off-by: Ryan Wang <i@ryanc.cc>
* feat: add initialized state to global info
* Refine setup page ui
Signed-off-by: Ryan Wang <i@ryanc.cc>
* refactor: improve the system initialization process
* Refine setup page ui
Signed-off-by: Ryan Wang <i@ryanc.cc>
* Refine setup page ui
Signed-off-by: Ryan Wang <i@ryanc.cc>
* fix: update with initialize state
* Refactor setup
Signed-off-by: Ryan Wang <i@ryanc.cc>
* refactor: initialization state
* Refactor router guards
Signed-off-by: Ryan Wang <i@ryanc.cc>
* Refine i18n
Signed-off-by: Ryan Wang <i@ryanc.cc>
* Refactor init data
Signed-off-by: Ryan Wang <i@ryanc.cc>
* Refactor init data
Signed-off-by: Ryan Wang <i@ryanc.cc>
* Update console/src/views/system/Setup.vue
Co-authored-by: Takagi <mail@e.lixingyong.com>
* refactor: initialization interface
---------
Signed-off-by: Ryan Wang <i@ryanc.cc>
Co-authored-by: Ryan Wang <i@ryanc.cc>
Co-authored-by: Takagi <mail@e.lixingyong.com>
#### What type of PR is this?
/kind feature
/area core
/milestone 2.9.x
#### What this PR does / why we need it:
Support restarting Halo and enable restart endpoint by default.
Restart endpoint detail:
request uri: `/actuator/restart`
request method: `POST`
Please note that memory usage may slightly increase after restarting Halo.
#### Does this PR introduce a user-facing change?
```release-note
支持在线重启 Halo。
```
#### What type of PR is this?
/kind bug
/area console
#### What this PR does / why we need it:
在 AnnotationsForm 新增 customAnnotationsDuplicateKey 校验规则，校验自定义元数据中是否具有重复的 key。
#### Which issue(s) this PR fixes:
Fixes#4367
#### Special notes for your reviewer:
在任意一个使用 AnnotationsForm 的位置，例如`文章设置 - 元数据` 中，新增一个已经存在的 key，查看是否有重复 key 的校验。
#### Does this PR introduce a user-facing change?
```release-note
修复 AnnotationsForm 重复的 key 校验无效的问题。
```
#### What type of PR is this?
/kind bug
/area console
#### What this PR does / why we need it:
为 AnnotationsForm 的 formkit 表单 id 增加 uuid 前缀，防止由于一个页面具有多个 AnnotationsForm 时编号互相冲突。
#### Which issue(s) this PR fixes:
Fixes#4368
#### Special notes for your reviewer:
检查使用 AnnotationsForm 的界面，例如文章、页面设置的元数据处没有出现问题即可。
#### Does this PR introduce a user-facing change?
```release-note
None
```
#### What type of PR is this?
/kind improvement
/area console
#### What this PR does / why we need it:
为 `Formkit` 添加自动滚动至错误的插件，当表单校验不通过时，如果错误处被隐藏，则会滚动至错误处。
#### Which issue(s) this PR fixes:
Fixes#4317
#### Special notes for your reviewer:
找到表单中的必选项或其他校验项，尝试填写一个错误的选项。之后滚动表单直到隐藏当前项，此时点击提交，查看是否能够自动滚动至对应的错误项。
#### Does this PR introduce a user-facing change?
```release-note
当表单填写错误时，将会自动滚动至错误项。
```
#### What type of PR is this?
/kind bug
/area console
#### What this PR does / why we need it:
在用户列表中，禁止用户选中自己，以解决用户能够进行视觉上自我删除的 bug。
<img width="1636" alt="image" src="https://github.com/halo-dev/halo/assets/31335418/d95f7cf5-cfea-49fa-8f68-d13c46bc88c1">
#### Which issue(s) this PR fixes:
Fixes#4350
#### Special notes for your reviewer:
#### Does this PR introduce a user-facing change?
```release-note
在用户列表中禁用选中当前用户
```
Ryan Wang