#### 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 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 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
```
#### What type of PR is this?
/kind improvement
/area core
/milestone 2.2.x
#### What this PR does / why we need it:
主题端显示当前用户创建的未审核通过的评论/回复
在开启了评论审核功能的前提下：
- 如果非匿名用户在主题端创建的评论或回复必须审核通过才能显示。
- 如果用户登录后评论或回复会被立即展示在列表，但仅限创建者可见，审核通过后对所有人可见。
#### Which issue(s) this PR fixes:
Fixes#2731
#### 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 improvement
/area core
/milestone 2.2.x
#### What this PR does / why we need it:
修复引入外部依赖的插件以开发模式启动时会出现 NoClassDefFoundError 的问题
see #3107 for more detail.
#### Which issue(s) this PR fixes:
Fixes#3107
#### Special notes for your reviewer:
how to test it?
以插件 development 模式启动以下两个插件观察是否正常启动：
- https://github.com/halo-sigs/plugin-s3
- https://github.com/halo-sigs/plugin-alioss
期望没有 `Caused by: java. lang. NoClassDefFoundEenon` 错误，且插件正确启动。
/cc @halo-dev/sig-halo
#### Does this PR introduce a user-facing change?
```release-note
修复引入外部依赖的插件以开发模式启动时会出现 NoClassDefFoundError 的问题
```
#### What type of PR is this?
/kind improvement
/milestone 2.2.x
#### What this PR does / why we need it:
文章和自定义页面支持展示最后修改时间
- 文章发布后会同步 post.spec.releasedSnapshot 记录的最后修改时间到 post.status.lastModifyTime，自定义页面亦如是。
- 主题端可以通过 `${item.status.lastModifyTime}` 获取（item表示文章或自定义页面 Vo）。
#### Which issue(s) this PR fixes:
Fixes#3090
#### 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 documentation
#### What this PR does / why we need it:
- Use arguments instead of environments.
- Change Docker image halo:2.0 into halo:2.1
#### Does this PR introduce a user-facing change?
```release-note
None
```
#### What type of PR is this?
/kind cleanup
/area core
#### What this PR does / why we need it:
Bump version to 2.2.0-SNAPSHOT for next iteration.
#### 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:
将 theme-earth 默认主题升级到 1.1.1
#### Does this PR introduce a user-facing change?
```release-note
None
```
#### What type of PR is this?
/kind feature
/area core
/milestone 2.1.x
#### What this PR does / why we need it:
新增操作 annotations 的表达式对象
在 thymeleaf 模板中使用示例：
```html
<p th:text="${#annotations.get(user, 'background')}"></p>
<p th:text="${#annotations.getOrDefault(user, 'background', 'default-value')}"></p>
<p th:text="${#annotations.contains(user, 'background')}"></p>
```
#### Which issue(s) this PR fixes:
Fixes#3073
#### Special notes for your reviewer:
/cc @halo-dev/sig-halo
#### Does this PR introduce a user-facing change?
```release-note
新增 Annotations 表达式对象用于在 thymeleaf 中操作自定义模型的 annotations
```
#### What type of PR is this?
/kind improvement
/area core
/milestone 2.1.x
#### What this PR does / why we need it:
Add cache control and last modified headers for responses of static resources.
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/2966
#### Special notes for your reviewer:
We can check the response header of statis resources to know if the cache control is working correctly.
#### Does this PR introduce a user-facing change?
```release-note
完善静态资源的缓存策略
```
#### What type of PR is this?
/kind improvement
/area core
#### What this PR does / why we need it:
主题卸载时等待删除关联资源后再清除 Finalizer
see #2967 for more detail.
https://github.com/halo-dev/halo/issues/2967#issuecomment-1354384978
#### Which issue(s) this PR fixes:
how to test it?
- 在主题中多添加一个 AnnotationSetting 资源 yaml，测试主题删除是否正常。
- 对包 `org.springframework.retry` 开启 debug 日志后能在删除主题时看到类似如下日志：
```
16:33:02.822 [Test worker] DEBUG org.springframework.retry.support.RetryTemplate - Retry: count=0
16:33:03.128 [Test worker] DEBUG org.springframework.retry.support.RetryTemplate - Checking for rethrow: count=1
```
Fixes#2967
#### Special notes for your reviewer:
/cc @halo-dev/sig-halo
#### Does this PR introduce a user-facing change?
```release-note
主题卸载时等待删除关联资源后再清除 Finalizer
```
#### What type of PR is this?
/kind feature
#### What this PR does / why we need it:
为 MenuItem 模型添加 a 标签的 target 属性设置。
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/3063
#### Special notes for your reviewer:
测试方式请看：https://github.com/halo-dev/console/pull/805
#### Does this PR introduce a user-facing change?
```release-note
菜单项支持设置打开方式
```
#### What type of PR is this?
/kind improvement
/area core
/milestone 2.1.x
#### What this PR does / why we need it:
迁移后文章过多，当文章的 Reconciler 还没有执行完时访问 Console 端文章列表会因为 post.status 为 Null 出现 NPE 问题
使用文章的 status 时需要对其进行判空
/cherry-pick release-2.0
#### Which issue(s) this PR fixes:
Fixes#3066
#### Special notes for your reviewer:
/cc @halo-dev/sig-halo
#### Does this PR introduce a user-facing change?
```release-note
None
```
#### What type of PR is this?
/kind feature
/kind api-change
/area core
/milestone 2.1.x
#### What this PR does / why we need it:
- Configuring message source location and name enables i18n message resolution.
- Simple global error handler.
- Refactor some exceptions with `ResponseStatusException` to control what HTTP status and problem detail need to be returned.
**TODO**
- [x] Add more UTs.
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/3020
#### Special notes for your reviewer:
Steps to test:
1. Try to refine `src/main/resources/config/i18n/messages_zh.properties` and switch Browser language with Chinese.
2. Delibrately make a mistake as you wish and see the error tips in console.
3. Try to access one page which doesn't exist and see the rendered result.
#### Does this PR introduce a user-facing change?
```release-note
完成系统异常的国际化
```
#### What type of PR is this?
/kind feature
/milestone 2.1.x
/area core
#### What this PR does / why we need it:
新增 AnnotationSetting 自定义模型以扩展自定义元数据设置表单
主题安装/更新/重载时都会重新加载与 theme.yaml 同层级的其他 yaml，但只会保存 kind 为 Setting 和 AnnotationSetting的，主题卸载时会删除这些 yaml 资源
#### Which issue(s) this PR fixes:
Fixes#3005
#### Special notes for your reviewer:
how to test it?
- 修改影响到了主题安装、更新、重载和删除，需要检查这些功能是否正确加载了 Setting 和 AnnotationSetting
- 插件启动时初始化的 AnnotationSetting 在插件停止时会被删除
- 主题添加了 annotation setting 资源，使用非超级管理员也可以获取
/cc @halo-dev/sig-halo
#### Does this PR introduce a user-facing change?
```release-note
新增 AnnotationSetting 以扩展自定义元数据设置表单
```
#### What type of PR is this?
/kind bug
/area core
/milestone 2.1.x
#### What this PR does / why we need it:
- Add missing resources `"policies", "policytemplates", "groups"` in policy rules in attachment role templates.
- Correct `nonResourceURLs` and `verbs`
See https://github.com/halo-dev/halo/issues/3007 for more.
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/3007
#### Special notes for your reviewer:
Steps to test:
1. Start Halo and login with `admin`
2. Create a Role with `Attachment Manage` permission only
3. Create an user and assign the role to the user
4. Set password for the user
5. Log out current user and log in as the user created just now
6. Try to do various operations in attachment tab
- Create and list policy
- Create and list group
- Upload and list attachments
#### Does this PR introduce a user-facing change?
```release-note
修复附件权限定义的错误
```
#### What type of PR is this?
/kind improvement
#### What this PR does / why we need it:
引入对R2DBC的MariaDB的支持，增加例子配置
#### Special notes for your reviewer:
现在，Halo可以使用MariaDB数据库原生驱动了，摆脱MySQL驱动带来的连接问题。
- [x] 支持首次启动执行SQL脚本创建表
#### 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
支持 MariaDB 数据库连接
```
#### What type of PR is this?
/kind improvement
/area core
#### What this PR does / why we need it:
Upgrade to spring boot 3.0.1
#### Which issue(s) this PR fixes:
Fixes#3030
#### Special notes for your reviewer:
#### Does this PR introduce a user-facing change?
```release-note
NONE
```
What type of PR is this?
/kind feature
/kind api-change
What this PR does / why we need it:
添加一个方法可以根据分类树的任意一层级的名称查询子树
Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/2960
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?
```release-note
CategoryFinder 添加根据分类查询子分类树结构的方法
```
#### What type of PR is this?
/kind bug
/area core
#### What this PR does / why we need it:
修复自定义页面 Finder 中 getByName 方法没有返回访问量的问题
此问题为重构 #2918 时引入。
#### Which issue(s) this PR fixes:
Fixes#2992
#### Special notes for your reviewer:
/cc @halo-dev/sig-halo
#### Does this PR introduce a user-facing change?
```release-note
None
```
#### What type of PR is this?
/kind bug
#### What this PR does / why we need it:
To fix that default earth theme file not found in system initialization.
#### Which issue(s) this PR fixes:
Fixes#2910
#### Special notes for your reviewer:
#### Does this PR introduce a user-facing change?
```release-note
NONE
```
#### What type of PR is this?
/kind feature
/kind api-change
/area core
#### What this PR does / why we need it:
为主题和插件提供重置设置项 API
此 PR 会重新读取配置对应的 Setting 资源，从其中读取默认值后更新到现有的 ConfigMap 中替换其 data
see #2789 for more details
#### Which issue(s) this PR fixes:
Fixes#2789
#### Special notes for your reviewer:
how to test it?
1. 在主题设置或插件设置配置一些设置项后保存
2. 执行重置配置
3. 配置恢复为了 Setting 中指定的默认值
/cc @halo-dev/sig-halo
#### Does this PR introduce a user-facing change?
```release-note
为主题和插件提供重置设置项 API
```
#### What type of PR is this?
/kind improvement
#### What this PR does / why we need it:
通过在模板引擎管理器里添加clearCache方法，在升级主题后进行缓存刷新，让新模板内容生效。
#### Which issue(s) this PR fixes:
Fixes#2953
#### Special notes for your reviewer:
#### 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:
/kind api-change
#### Which issue(s) this PR fixes:
Fixes#2591
#### Special notes for your reviewer:
#### 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 separates security configuration of RESTful APIs and portal pages to configure specific headers for portal pages, such as `Referrer-Policy` and `X-Frame-Options`.
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/2900
#### Special notes for your reviewer:
You can see the response headers of index page:
```diff
HTTP/1.1 200 OK
Content-Type: text/html
Content-Language: en-US
+ X-Content-Type-Options: nosniff
+ X-Frame-Options: SAMEORIGIN
+ X-XSS-Protection: 0
+ Referrer-Policy: strict-origin-when-cross-origin
content-encoding: gzip
content-length: 4285
```
and request headers with `Referer`:
```diff
GET / HTTP/1.1
Host: localhost:8090
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:107.0) Gecko/20100101 Firefox/107.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
+ Referer: http://localhost:8090/archives/12341234
Connection: keep-alive
Cookie: _ga_Z907HJBP8W=GS1.1.1670164888.1.1.1670165603.0.0.0; _ga=GA1.1.807839437.1670164889; SESSION=539e060e-c11e-4b6d-a749-882905b30a88; XSRF-TOKEN=4b692b55-638c-4497-8a4b-be00986eda90
Upgrade-Insecure-Requests: 1
Sec-Fetch-Dest: document
Sec-Fetch-Mode: navigate
Sec-Fetch-Site: same-origin
Sec-Fetch-User: ?1
```
#### Does this PR introduce a user-facing change?
```release-note
解决访问分析工具无法显示 referer 的问题
```
<!-- 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#2958
#### Special notes for your reviewer:
/cc @halo-dev/sig-halo
#### 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 bug
<!--
添加其中一个类别：
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:
/kind api-change
#### 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#2951
#### 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 feature
/area core
#### What this PR does / why we need it:
主题端支持异常模板页面
异常模板必须放在主题目录的 `templates/error` 目录下：
- 支持按照 response status 名称模板页面，例如 404.html ，当发生 404 错误时会使用 404.html
- 支持 4xx.html、5xx.html，例如当发生 403 错误时，如果存在 403.html 则使用此页面，否则使用 4xx.html
error 模板中具有 model 示例:
```json
{
"error": {
"type": "about:blank",
"title": "Not Found",
"status": 404,
"detail": "Extension run.halo.app.core.extension.Plugin with name amet ut magn not found",
"instance": "/apis/plugin.halo.run/v1alpha1/plugins/amet%20ut%20magn"
}
}
```
#### Which issue(s) this PR fixes:
Fixes#2690
#### 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 improvement
/area core
#### What this PR does / why we need it:
HaloPluginManager 移除 getRootApplicationContext 方法
#### Which issue(s) this PR fixes:
Fixes#2943
#### Special notes for your reviewer:
/cc @halo-dev/sig-halo
#### Does this PR introduce a user-facing change?
```release-note
HaloPluginManager 移除 getRootApplicationContext 方法
```
#### What type of PR is this?
/kind improvement
/area core
#### What this PR does / why we need it:
Now, we can pass command-line arguments while using Docker. Please refer to <https://github.com/halo-dev/halo/issues/2902>.
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/2902
#### Special notes for your reviewer:
Steps to test:
1. Run Halo with command-line arguments:
```bash
docker run --rm -it -p6666:6666 johnniang/halo:support-command-line-args --server.port=6666
```
1. Request <http://localhost:6666>
```bash
curl -v http://localhost:6666
```
#### 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
支持命令行参数启动 Halo
```
#### What type of PR is this?
/kind feature
/area core
#### What this PR does / why we need it:
为主题端新增作者页面
see #2837 for more detail
#### Which issue(s) this PR fixes:
Fixes#2837
#### 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 improvement
/area core
/milestone 2.1.x
#### What this PR does / why we need it:
Force to add environment variables `HALO_WORK_DIR` and `SPRING_CONFIG_LOCATION` into Dockerfile. After that, we can configure `application.yaml` in working directory as we want.
Please note that we can not configure Halo working directory in `/root/.halo2/application.yaml` directly. Use environment variable `HALO_WORK_DIR` instead.
#### Which issue(s) this PR fixes:
Fixes https://github.com/halo-dev/halo/issues/2812
#### Special notes for your reviewer:
Steps to test:
1. Prepare custom configuration
```bash
mkdir -p halo2
cat <<EOF > halo2/application.yaml
server:
port: 12345
EOF
```
2. Start up Halo using Docker
```bash
docker run -it --rm -p12345:12345 -v `pwd`/halo2:/root/.halo2 johnniang/halo:configure-halo-in-work-dir
```
3. Request http://localhost:12345
```bash
curl -v localhost:12345
```
#### Does this PR introduce a user-facing change?
```release-note
支持在工作目录添加自定义配置
```
#### What type of PR is this?
/kind bug
/area core
#### What this PR does / why we need it:
修复插件 logo 为相对路径时先启用再停后就无法加载 logo 的问题
原因是 reverse proxy reconciler 资源被删除要取消注册路由时没有确切指定名称，logo 这样的 ReverseProxy 是插件安装时初始化的这条初始化的规则要跟随插件的生命周期，只有插件卸载时才会被删除，而在此之前插件被停止时就被误取消注册了
see #2937 for more detail
#### Which issue(s) this PR fixes:
Fixes#2937
#### Special notes for your reviewer:
/cc @halo-dev/sig-halo
#### Does this PR introduce a user-facing change?
```release-note
修复插件 logo 为相对路径时先启用再停后就无法加载 logo 的问题
```
#### What type of PR is this?
/kind bug
/area core
#### What this PR does / why we need it:
修复插件开发模式下后续增加的 fixedPluginPath 项无法被加载的问题
- 目前启动时会加载 pluginRepository 的所有 path，fixedPluginPath 被 DefaultDevelopmentPluginRepository 管理，所以在遍历 fixedPluginPath 加载时可能已经被加载过，需要判断是否被加载过，但即使被加载过也不能跳过而要继续执行创建/更新 plugin.yaml 资源的逻辑
- 创建/更新 plugin.yaml 时需要使用重试机制防止因为乐观锁冲突导致 Halo 无法启动
see #2939 for more detail
#### Which issue(s) this PR fixes:
Fixes#2939
#### Special notes for your reviewer:
/cc @halo-dev/sig-halo
#### Does this PR introduce a user-facing change?
```release-note
修复插件开发模式下后续增加的 fixedPluginPath 项无法被加载的问题
```
John Niang
