#### What type of PR is this?
/kind improvement
#### What this PR does / why we need it:
修复 Actuator 页面抖动的问题。
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/3225
#### Special notes for your reviewer:
测试方式：
1. 测试进入系统概览页面是否会出现 https://github.com/halo-dev/halo/issues/3225 中提到的页面抖动问题。
#### Does this PR introduce a user-facing change?
```release-note
修复 Console 端进入系统概览页面会抖动的问题。
```
#### What type of PR is this?
/kind improvement
/area core
/milestone 2.3.x
#### What this PR does / why we need it:
当开发模式启动时上传 JAR 运行插件会出现插件不存在的异常，但由于 PluginReconciler 中检查状态不一致后 return 在 optional 语句中只是让当前 optional 后面的代码停止执行，还会继续执行 optional 外面的代码导致 status 的异常信息不一致，进而 object equals 始终为 false 而无法让 reconciler 终止运行导致循环。
此 PR 调整了一下代码位置，进入 reconciler 时先进行检查，如果不满足则不执行后面的代码同时将信息写入 plugin.status 让用户知晓。
此问题是修改了 Reconciler 判断逻辑后出现的 https://github.com/halo-dev/halo/pull/3210 ，因此不影响之前的代码只针对当前 2.3.x
#### Special notes for your reviewer:
how to test it?
1. 模拟一个插件找不到的错误场景例如以生产模式启动插件但配置 fixed-plugin 指定为插件项目目录
2. 启动 Halo 看 Reconciler 是否会一直在控制台输出日志
3. 卸载它能成功
/cc @halo-dev/sig-halo
#### Does this PR introduce a user-facing change?
```release-note
None
```
#### What type of PR is this?
/kind improvement
/area core
#### What this PR does / why we need it:
Save ThemeContext into ServerWebExchange to reduce the number of queries to resolve theme from 2(or 3) to 1.
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/3162
#### 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 端 FormKit 的 Code 输入类型宽度异常
#### Which issue(s) this PR fixes:
Fixes # https://github.com/halo-dev/halo/issues/3227
#### Special notes for your reviewer:
#### Does this PR introduce a user-facing change?
```release-note
修复 Console 端 FormKit 的 Code 输入框宽度未占满的问题
```
#### What type of PR is this?
/kind improvement
/area core
/milestone 2.3.x
#### What this PR does / why we need it:
I create another exception `DuplicateNameException` to map `org.springframework.dao.DuplicateKeyException` when creating extensions.
See https://github.com/halo-dev/halo/issues/3180 for more.
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/3180
#### Special notes for your reviewer:
1. Try to create an user which name has already exist
2. See the error
#### Does this PR introduce a user-facing change?
```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 improvement
/area console
<!--
添加其中一个类别：
Add one of the following kinds:
/kind bug
/kind cleanup
/kind documentation
/kind feature
/kind optimization
适当添加其中一个或多个类别（可选）：
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:
添加`X-Requested-With=XMLHttpRequest`请求头，以阻止spring security 带上`WWW-Authenticate`响应头导致弹出原生登录框。
#### 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/3213
#### Screenshots:
<!--
如果此 PR 有 UI 的改动，最好截图说明这个 PR 的改动。
If there are UI changes to this PR, it is best to take a screenshot to illustrate the changes to this PR.
eg.
Before:
After:
-->
#### Special notes for your reviewer:
使session过期后（直接删除cookie的session或重启后端），继续操作console端，预期不会弹出原生登录框且console端原有的重新登录form正常弹出。
详情https://spring.io/guides/tutorials/spring-security-and-angular-js/ 中搜索X-Requested-With
#### 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?
/kind improvement
/area core
/milestone 2.3.x
#### What this PR does / why we need it:
1. Refactor Queue in Controller. I add dirty set of request to avoid lost of new request from other places instead of reconciler.
2. Enhance equals and hashcode methods to ensure we can ignore updates of same extensions.
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/2860
#### Special notes for your reviewer:
Please take some time to test publishing posts.
#### Does this PR introduce a user-facing change?
```release-note
修复发布文章时经常出现错误的问题
```
#### What type of PR is this?
/kind bug
/area core
/milestone 2.2.x
#### What this PR does / why we need it:
修复重复安装插件时 JAR 文件被删除的问题
需要注意的场景：
prod 模式下，假如安装一个 sitemap 插件，版本为 1.0.0 ，而此时 plugins 目录已经存在同名文件 sitemap-1.0.0.jar 文件但 sitemap 的 plugin.yaml 没有被持久化过，则能正常安装，旧的 JAR 文件被覆盖。
see #3159 for more details
#### Which issue(s) this PR fixes:
Fixes#3159
#### Special notes for your reviewer:
/cc @halo-dev/sig-halo
#### Does this PR introduce a user-facing change?
```release-note
修复重复安装插件时 JAR 文件被删除的问题
```
#### What type of PR is this?
/kind cleanup
/area core
#### What this PR does / why we need it:
Bump Halo version to 2.3.0-SNAPSHOT and update README.md
#### 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:
发布 Console 2.2.0
#### Does this PR introduce a user-facing change?
```release-note
None
```
#### What type of PR is this?
/kind feature
#### What this PR does / why we need it:
添加复制或者拖拽图片到编辑器上传的支持。
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/3109
Fixes https://github.com/halo-dev/halo/issues/2946
#### Screenshots:
#### Special notes for your reviewer:
#### Does this PR introduce a user-facing change?
```release-note
Console 端的默认编辑器支持拖拽或者粘贴图片上传
```
#### What type of PR is this?
/kind bug
#### What this PR does / why we need it:
修复在开发环境下首次初始化后，没有加载默认主题的情况下无法访问主题管理页面的问题。
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/3187
#### Special notes for your reviewer:
测试方式：
1. 在开发环境使用全新的数据库初始化。
2. 检查是否能够正常的访问主题管理页面。
#### Does this PR introduce a user-facing change?
```release-note
None
```
#### What type of PR is this?
/kind bug
/area core
/milestone 2.2.x
#### What this PR does / why we need it:
Make requires field of Theme not required.
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/3177
#### Special notes for your reviewer:
1. Clear Halo working directory
2. Start Halo freshly
#### Does this PR introduce a user-facing change?
```release-note
None
```
#### What type of PR is this?
/kind improvement
/area core
/milestone 2.2.x
#### What this PR does / why we need it:
See https://lucene.apache.org/core/9_5_0/MIGRATE.html for more.
#### Special notes for your reviewer:
Please confirm that the search widget is working fine.
#### Does this PR introduce a user-facing change?
```release-note
升级依赖 Lucene 至 9.5.0
```
#### What type of PR is this?
/kind imporvement
/area core
/milestone 2.2.x
#### What this PR does / why we need it:
See 2d3cf24fed/CHANGELOG.md (390---2023-01-30) for more.
#### Special notes for your reviewer:
Please confirm that the plugin module is working fine.
#### Does this PR introduce a user-facing change?
```release-note
升级依赖 PF4J 至 3.9.0
```
#### What type of PR is this?
/kind improvement
/area core
/milestone 2.2.x
#### What this PR does / why we need it:
See https://github.com/jasync-sql/jasync-sql/releases/tag/2.1.23 for more.
#### Does this PR introduce a user-facing change?
```release-note
升级依赖 jasync-sql 至 2.1.13
```
#### What type of PR is this?
/kind improvement
#### What this PR does / why we need it:
修改获取文章和自定义页面内容的 API，用于适配：https://github.com/halo-dev/halo/pull/3168
#### Special notes for your reviewer:
测试方式：
1. 测试文章和自定义页面编辑时，能否正常获取内容即可。
#### Does this PR introduce a user-facing change?
```release-note
None
```
#### What type of PR is this?
/kind feature
/area core
/milestone 2.2.x
#### What this PR does / why we need it:
Provide `globalconfig` actuator endpoint to let console and theme know how to do according various system configuration. The endpoint allows anonymous users to access, but other actuator endpoints can be accessed by admin users.
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/3055
#### Special notes for your reviewer:
Try to request <http://localhost:8090/actuator/globalinfo> and see the result.
```json
{
"externalUrl":"http://localhost:8090",
"timeZone":"Asia/Shanghai",
"locale":"en_US",
"allowComments":true,
"allowRegistration":false
}
```
You can request <http://localhost:8090/actuator/info> to see more detail as well.
```json
{
"git": {
"branch": "feat/system-info",
"commit": {
"id": "ca4e93d",
"time": "2023-01-19T08:56:15Z"
}
},
"build": {
"artifact": "halo",
"name": "halo",
"time": "2023-01-29T15:04:42.151Z",
"version": "2.2.0-SNAPSHOT",
"group": "run.halo.app"
},
"java": {
"version": "17.0.6",
"vendor": {
"name": "Amazon.com Inc.",
"version": "Corretto-17.0.6.10.1"
},
"runtime": {
"name": "OpenJDK Runtime Environment",
"version": "17.0.6+10-LTS"
},
"jvm": {
"name": "OpenJDK 64-Bit Server VM",
"vendor": "Amazon.com Inc.",
"version": "17.0.6+10-LTS"
}
},
"os": {
"name": "Windows 11",
"version": "10.0",
"arch": "amd64"
}
}
```
#### Does this PR introduce a user-facing change?
```release-note
提供系统配置详情端口
```
#### What type of PR is this?
/kind improvement
/area core
/milestone 2.2.x
/kind api-change
#### What this PR does / why we need it:
优化文章和自定义页面的内容查询
- 文章新增 `GET /posts/{name}/release-content` 和 `GET /posts/{name}/head-content` 自定义 APIs
- 自定义页面新增 `GET /posts/{name}/release-content` 和 `GET /posts/{name}/head-content` 自定义 APIs
⚠️ 移除了 ContentEndpoint，如果 Console 调用过 `/apis/api.console.halo.run/contents/{name}` 查询内容则需要用文章或自定义页面的自定义APIs 替代
#### Which issue(s) this PR fixes:
Fixes#3140
Fixes https://github.com/halo-dev/halo/issues/3026
#### Special notes for your reviewer:
/cc @halo-dev/sig-halo
#### Does this PR introduce a user-facing change?
```release-note
优化文章和自定义页面的内容查询
```
#### What type of PR is this?
/kind feature
/milestone 2.2.x
#### What this PR does / why we need it:
文章、独立页面、分类、标签支持自动生成别名。
策略：
1. 仅在创建时会自动根据标题或者名称自动生成别名，编辑时如果需要重新生成，可以点击输入框右侧的按钮。
2. 中文会被转为拼音并用 - 隔开，需要注意多音字的情况，目前无法保证多音字是否符合预期。
3. 使用了 https://www.npmjs.com/package/transliteration 库。
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/3171
#### Screenshots:
<img width="782" alt="image" src="https://user-images.githubusercontent.com/21301288/213849446-18d70974-7b2c-420c-bd50-93d2c3193895.png">
#### Special notes for your reviewer:
测试方式：
1. 需要 `pnpm install`
4. 测试文章、独立页面、分类、标签创建时，是否可以自动设置别名。
5. 测试别名输入框右侧的生成别名按钮是否正常工作。
6. 测试分类和标签选择器创建新分类或标签时，是否正确设置了别名。
#### Does this PR introduce a user-facing change?
```release-note
Console 端的文章、独立页面、分类、标签支持自动生成别名
```
#### What type of PR is this?
/kind improvement
/milestone 2.2.x
#### What this PR does / why we need it:
使用新的 API 来管理插件，用于区分插件管理和配置相关的权限。适配：https://github.com/halo-dev/halo/pull/3142
#### Which issue(s) this PR fixes:
Ref https://github.com/halo-dev/halo/issues/3069
#### Screenshots:
#### Special notes for your reviewer:
测试方式：
1. Halo 需要切换到 https://github.com/halo-dev/halo/pull/3142 分支。
2. Console 需要 `pnpm install`。
1. 插件设置项，需要测试保存，安装新插件之后表单是否正常。
3. 创建一个角色，测试仅有管理/查看插件的角色，登录之后检查是否符合预期。
#### 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:
使用新的 API 来管理主题，用于区分主题管理和配置相关的权限。适配：https://github.com/halo-dev/halo/pull/3135
#### Which issue(s) this PR fixes:
Ref https://github.com/halo-dev/halo/issues/3069
#### Screenshots:
#### Special notes for your reviewer:
重点测试：
1. Halo 需要切换到 https://github.com/halo-dev/halo/pull/3135 分支。
2. Console 需要 `pnpm install`。
1. 主题设置项，需要测试保存，安装新主题之后表单是否正常。
3. 创建一个角色，测试仅有管理/查看主题的角色，登录之后检查是否符合预期。
#### Does this PR introduce a user-facing change?
```release-note
重构 Console 端主题的设置表单逻辑。
```
#### What type of PR is this?
/kind improvement
/area core
/kind api-change
/milestone 2.2.x
#### What this PR does / why we need it:
添加自定义 APIs 以分离插件对 Setting 和 ConfigMap 权限的依赖
⚠️ 此 PR 新增了 APIs，需要 Console 对其进行适配，插件查询 Setting、ConfigMap 的 APIs 需要更改。
#### Which issue(s) this PR fixes:
A part of https://github.com/halo-dev/halo/issues/3069
Fixes https://github.com/halo-dev/halo/issues/3069
#### Special notes for your reviewer:
how to test it?
- 测试 GET /plugins/{name}/setting 是否能正确获取到插件名称对应的主题的 Setting。
- 测试 GET /plugins/{name}/config 是否能正确获取到插件名称对应的主题的 ConfigMap。
- 测试 PUT /plugins/{name}/config 是否能更新插件的 ConfigMap，如果名称不匹配则抛出异常。
切换用户为其分配主题的查看权限可以有权限调用以上描述的 GET 请求的 endpoints，管理权限可以调用 PUT /plugins/{name}/config。
/cc @halo-dev/sig-halo
#### Does this PR introduce a user-facing change?
```release-note
添加自定义 APIs 以分离插件对 Setting 和 ConfigMap 权限的依赖
```
#### What type of PR is this?
/kind feature
/milestone 2.2.x
/area core
/kind api-change
#### What this PR does / why we need it:
添加自定义 APIs 以分离主题对 Setting 和 ConfigMap 权限的依赖
⚠️ 此 PR 新增了 APIs，需要 Console 对其进行适配，主题菜单下获取激活主题的 API 以及查询主题 Setting、ConfigMap 的 APIs 需要更改。
#### Which issue(s) this PR fixes:
A part of #3069
Fixes https://github.com/halo-dev/halo/issues/3069
#### Special notes for your reviewer:
how to test it?
- 测试 `GET /themes/-/activation` 此 endpoint 是否能正确获取到激活主题信息
- 测试 `GET /themes/{name}/setting` 是否能正确获取到主题名称对应的主题的 Setting，如果 name 为 `-` 表示查询当前激活主题的 Setting
- 测试 `GET /themes/{name}/config` 是否能正确获取到主题名称对应的主题的 ConfigMap, 如果 name 为 `-` 表示查询当前激活主题的 ConfigMap。
- 测试 `PUT themes/{name}/config` 是否能更新主题的 ConfigMap，如果名称不匹配则抛出异常。
切换用户为其分配主题的查看权限可以有权限调用以上描述的 GET 请求的 endpoints，管理权限可以调用 `PUT themes/{name}/config`。
- 测试 `PUT /themes/{name}/activation` 是否能设置激活主题。
/cc @halo-dev/sig-halo
#### Does this PR introduce a user-facing change?
```release-note
添加自定义 APIs 以分离主题对 Setting 和 ConfigMap 权限的依赖
```
#### What type of PR is this?
/kind improvement
/area core
/milestone 2.2.x
#### What this PR does / why we need it:
Upgrade Spring Boot to 3.0.2.
See https://github.com/spring-projects/spring-boot/releases/tag/v3.0.2 for more.
#### Does this PR introduce a user-facing change?
```release-note
升级依赖 Spring Boot 至 3.0.2
```
#### What type of PR is this?
/kind bug
/area core
/milestone 2.2.x
#### What this PR does / why we need it:
Remove URI decode operation while inserting key into RadixRouterTree to avoid repeat decode.
#### Which issue(s) this PR fixes:
Fixes#3178
#### Special notes for your reviewer:
1. Set slug name to `1%1` when creating a post
2. Publish it
3. Browse the post
#### Does this PR introduce a user-facing change?
```release-note
修复因别名包含百分号导致无法正常访问的问题
```
#### What type of PR is this?
/kind improvement
/area core
/milestone 2.2.x
#### What this PR does / why we need it:
插件安装后根据配置的 settingName 读取默认值创建 ConfigMap
如果配置了 settingName 而没有配置 configMapName 则会自动填充为 uuid 并创建一个 ConfigMap
#### Which issue(s) this PR fixes:
Fixes#3160
#### Special notes for your reviewer:
/cc @halo-dev/sig-halo
#### Does this PR introduce a user-facing change?
```release-note
插件安装后自动初始化 Setting 的默认值
```
#### What type of PR is this?
/kind bug
/area core
#### What this PR does / why we need it:
Currently, if there is no `error.html` error template in theme, but there is a `404.html` error template, this will not work correctly.
We always get rendering result from global error template `error.html`.
This PR mainly provides a `ThemeTemplateAvailabilityProvider` to check if the template is available in theme instead of in globally predefined templates.
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/3062
#### Special notes for your reviewer:
1. Download and install any theme
2. Check the theme folder
3. Check folder `templates/error`
4. Try to remove `templates/error/error.html` template file
5. Create `templates/error/404.html`
6. Request a page which does not exist
7. See the result
#### Does this PR introduce a user-facing change?
```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 bug
<!--
添加其中一个类别：
Add one of the following kinds:
/kind bug
/kind cleanup
/kind documentation
/kind feature
/kind optimization
适当添加其中一个或多个类别（可选）：
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:
修复后台删除评论后会导致下方头像错误的bug
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/3170
<!--
PR 合并时自动关闭 issue。
Automatically closes linked issue when PR is merged.
用法：`Fixes #<issue 号>`，或者 `Fixes (粘贴 issue 完整链接)`
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->
#### Screenshots:
<!--
如果此 PR 有 UI 的改动，最好截图说明这个 PR 的改动。
If there are UI changes to this PR, it is best to take a screenshot to illustrate the changes to this PR.
eg.
Before:
After:
-->
#### 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
修复后台删除评论后会导致下方头像错误的bug
```
<!-- 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
/area core
<!--
添加其中一个类别：
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:
Display archives in reverse chronological order.
#### 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/3157
#### 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?
/kind improvement
#### What this PR does / why we need it:
优化 Console 端加载插件资源的逻辑。
1. 查询接口改为自定义接口，传入 enabled 参数进行筛选。
2. 修改符合 Console 插件的筛选判断。
3. 隐藏加载异常的提示。
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/3156
#### Special notes for your reviewer:
测试方式：
1. 安装若干带有 Console 端拓展的插件，比如：https://github.com/halo-sigs/plugin-stackedit
2. 检查是否有加载成功。
3. 创建一个没有插件访问权限的角色。
4. 登录之后检查是否有无权限提示。
#### Does this PR introduce a user-facing change?
```release-note
优化 Console 端加载插件资源的逻辑。
```
#### What type of PR is this?
/kind bug
/area core
/milestone 2.2.x
#### What this PR does / why we need it:
This PR mainly customizes AnonymousAuthenticationWebFilter and SpringSecurityDialect to make authentication visible in exception web handler. So that we can get SecurityContext while rendering error page.
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/3133
#### Test steps
1. Start Halo
2. Request a page which is not found
3. See upper right corner icon
#### Does this PR introduce a user-facing change?
```release-note
修复错误模板渲染无法获取登录信息的问题
```
#### What type of PR is this?
/kind feature
/kind improvement
#### What this PR does / why we need it:
Update comments default sorter for console
#### Which issue(s) this PR fixes:
Fixes#3138
#### Special notes for your reviewer:
#### Does this PR introduce a user-facing change?
```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 improvement
/area core
<!--
添加其中一个类别：
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:
Provide administrators with the ability to adjust the order of articles by modifying the publish time.
#### 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/3143
#### 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?
/kind improvement
/area core
#### What this PR does / why we need it:
When we [implemented theme mechanism](https://github.com/halo-dev/halo/pull/2280), some problems of thymeleaf came up in front of us, especially TemplateEngine. So we copied full code of SpringTemplateEngine and SpringWebFluxTemplateEngine and made minor changes to adapt our requirements.
Fortunately, issue https://github.com/thymeleaf/thymeleaf/issues/901 I fired has been fixed, and we have a chance to optimize this part of the code.
See https://github.com/halo-dev/halo/issues/3070 for more.
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/3070
#### Special notes for your reviewer:
Hope reviewers test various endpoints.
#### Does this PR introduce a user-facing change?
```release-note
None
```
#### What type of PR is this?
/kind improvement
/area core
#### What this PR does / why we need it:
This PR adapt web properties to control cache of static resources.
Users who want to disable cache can configure like this:
```yaml
spring:
web:
resources:
cache:
cachecontrol:
no-cache: true
use-last-modified: false
```
By default, we have disabled cache in development environment.
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/3127
#### Does this PR introduce a user-facing change?
```release-note
None
```
Ryan Wang
