添加代码块 dart 语言的高亮
<!-- Thanks for sending a pull request! Here are some tips for you:
1. 如果这是你的第一次，请阅读我们的贡献指南：<https://github.com/halo-dev/halo/blob/main/CONTRIBUTING.md>。
1. If this is your first time, please read our contributor guidelines: <https://github.com/halo-dev/halo/blob/main/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 editor
<!--
添加其中一个类别：
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:
> 为默认编辑器的代码块导入 dart 语言高亮
#### Which issue(s) this PR fixes:
Fixes#5530
<!--
PR 合并时自动关闭 issue。
Automatically closes linked issue when PR is merged.
用法：`Fixes #<issue 号>`，或者 `Fixes (粘贴 issue 完整链接)`
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->
#### 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
为需要代码块dart语言高亮的用户提供支持
```
#### What type of PR is this?
/area editor
/area ui
/kind feature
#### What this PR does / why we need it:
为默认编辑器添加标题输入框。
<img width="1665" alt="image" src="https://github.com/halo-dev/halo/assets/21301288/df903e02-76b0-45fe-89d9-6ac81af8f041">
#### Which issue(s) this PR fixes:
Fixes#5427
#### Special notes for your reviewer:
#### Does this PR introduce a user-facing change?
```release-note
为默认编辑器添加标题输入框。
```
#### What type of PR is this?
/kind bug
/area editor
/area ui
/milestone 2.14.x
#### What this PR does / why we need it:
在默认的富文本编辑器中，使用了 [tiptap link](b3ef574f3d/packages/extension-link/src/link.ts (L127C3-L135C5)) ，而其中的 renderHTML 会对 href 进行处理，但当链接为纯数字的时候，`HTMLAttributes.href` 将不会有 `startsWith` 方法。
此 PR 将在解析 renderHTML 时，将 `HTMLAttributes.href` 转为 string，进而解决这个问题。
#### How to test it?
测试使用默认富文本编辑器时，编写一个链接，并将其设置为纯数字。
刷新页面，查看是否具有报错。
#### Which issue(s) this PR fixes:
Fixes#5478
#### Does this PR introduce a user-facing change?
```release-note
解决在默认富文本编辑器中当链接为纯数字时报错的问题
```
#### What type of PR is this?
/kind improvement
/area core
/milestone 2.14.x
#### What this PR does / why we need it:
使用索引机制优化回复功能的查询以提高查询速度
#### Does this PR introduce a user-facing change?
```release-note
使用索引机制优化回复功能的查询以提高查询速度
```
#### What type of PR is this?
/kind improvement
/area core
/milestone 2.14.x
#### What this PR does / why we need it:
使用索引机制优化评论数据查询以提高效率
how to test it?
- 测试 console 评论列表和筛选条件是否正确
- 测试主题端评论显示是否正确
#### Does this PR introduce a user-facing change?
```release-note
使用索引机制优化评论数据查询以提高效率
```
#### What type of PR is this?
/kind improvement
/area editor
/area ui
/milestone 2.14.x
#### What this PR does / why we need it:
将默认富文本编辑器中的链接中的 rel 属性由默认的 `noopener noreferrer nofollow` 属性改为 null，优化 SEO 。
#### How to test it?
查看使用默认富文本编辑器创建的链接，其 rel 属性是否不再是 `noopener noreferrer nofollow`
#### Which issue(s) this PR fixes:
Fixes#5328
#### Does this PR introduce a user-facing change?
```release-note
移除默认富文本编辑器中链接的 nofollow 等属性，优化 SEO。
```
#### What type of PR is this?
/area editor
/area ui
/kind feature
/milestone 2.14.x
#### What this PR does / why we need it:
为默认富文本编辑器中的表格，增加全选快捷键。具体操作逻辑如下：
1. 当光标处于表格中单元格内时，按 `Mod + a` 全选快捷键后，若未选中当前单元格，则选中单元格。
2. 若其中包含有其他影响全选快捷键的组件，则以组件自身为准，例如代码块中的全选。
3. 若已经选中单元格，则再次按全选快捷键，选中整个表格。
4. 若已经选中表格，则再按全选快捷键不会触发其他全选事件。
#### How to test it?
按照操作逻辑测试全选快捷键逻辑是否无误。是否与其他快捷键产生冲突。
#### Which issue(s) this PR fixes:
Fixes#5438
#### Does this PR introduce a user-facing change?
```release-note
为富文本编辑器中的表格组件增加全选快捷键
```
#### What type of PR is this?
/kind cleanup
/area core
#### What this PR does / why we need it:
Bump version to 2.14 to prepare for developing 2.14. This always happens after new version is released.
#### Does this PR introduce a user-facing change?
```release-note
None
```
### What type of PR is this?
/kind improvement
/area core
/milestone 2.13.x
### What this PR does / why we need it:
使用索引机制优化通知和订阅查询以提高性能
how to test it
测试通知列表不报错即可
### Does this PR introduce a user-facing change?
```release-note
使用索引机制优化通知和订阅查询以提高性能
```
#### 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:
升级 Vue 生态相关依赖至最新版本。
#### Does this PR introduce a user-facing change?
```release-note
升级 Vue 生态相关依赖至最新版本。
```
#### 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?
/kind bug
/area editor
/area console
#### What this PR does / why we need it:
在 #5191 中对表格新增了如果可以左右滚动时，则显示阴影的特性。而根据 `prosemirror` 的数据流处理策略，在 `decorations` 中，state 是 new EditorState，但通过 `this.editor.view` 获取到的 view 为 old EditorView，进而导致使用了最新的坐标，并且使用其坐标通过旧版本的 view 中获取 DOM 而产生的错误。
本 PR 使用 `NodeView` 而不是 `decorations` 来重新处理表格阴影。
#### How to test it?
在默认富文本编辑器中新建一个表格。在表格前使用拼音输入文本，查看此文本能否被输入。
同时查看表格阴影是否存在
#### Which issue(s) this PR fixes:
Fixes#5352
#### Does this PR introduce a user-facing change?
```release-note
解决默认富文本编辑器表格前字符无法被编辑的问题。
```
#### What type of PR is this?
/kind improvement
/area core
/milestone 2.13.x
#### What this PR does / why we need it:
使用索引功能优化附件列表查询
#### Does this PR introduce a user-facing change?
```release-note
使用索引功能优化附件列表查询
```
#### What type of PR is this?
/area ui
/kind cleanup
#### What this PR does / why we need it:
Rename console to ui in some files,
Ref https://github.com/halo-dev/halo/pull/5314
#### Does this PR introduce a user-facing change?
```release-note
None
```
SakuraZ