feat: Fixed the pathPrefix generation error in the OpenAPI document.

[CaroLe-prw]

The original prefix created by pathPrefix has been overridden with a new predefined value.

[github-actions]

@CaroLe-prw

🔍 Before proceeding, please review the contribution guidelines

• 📖 Contribution Guide

This includes requirements for:

• ✅ Commit message format (Angular Convention. feat, fix, etc.)
• 🧹 Code style (execute mvn spring-javaformat:apply)
• 📄 Documentation updates (if config changes)
• 💡 Example code submission (for new features)

Thanks for your PR. 🙏
Please check again for your PR changes whether they contain any usage configuration change, such as Add new configuration or Change default value of configuration.
If so, please add or update documents (Markdown format) in the docs/ directory of the repository smart-doc-group/smart-doc-group.github.io.

In addition, if you have added new features, please provide example code in the repository smart-doc-group/smart-doc-example-cn. This will help other users understand how to use the new features.

Code Style Reminder:
The code should use the Spring code style. Please format your code using the command mvn spring-javaformat:apply. You can also install the Spring Java Format plugin for convenience.

---

🔍 提交前请务必完成以下检查

• 📘 贡献指南

需特别注意：

• ✅ 提交信息格式 (feat, fix 等类型)
• 🧹 代码风格（执行 mvn spring-javaformat:apply）
• 📄 文档更新（配置变更需同步更新 docs）
• 💡 示例代码（新功能需提供示例）

感谢您提交的PR。 🙏
请再次查看您的PR内容，确认是否包含任何使用方式或配置参数的变更，如：新增配置参数、修改默认配置等操作。
如果是，请确保在提交之前，在仓库smart-doc-group/smart-doc-group.github.io中的docs/目录下添加或更新文档（Markdown格式）。

另外，如果您添加了新功能，请在仓库smart-doc-group/smart-doc-example-cn中提供示例代码。这将帮助其他用户了解如何使用新功能。

代码风格提示：
请使用 Spring 代码风格。您可以通过命令 mvn spring-javaformat:apply 格式化代码。为了方便操作，您还可以安装 Spring Java Format 插件。

[linwumingshi]

@CaroLe-prw Hi, this code was originally introduced in PR #1057 to resolve issues #1046. After its removal in this PR, would the fix for #1046 still hold effectively? Would you consider adding targeted regression tests to ensure backward compatibility? Your insights would be appreciated.

---

请问，这部分代码最初是 PR #1057 为解决 issues #1046 引入的。当前 PR 移除该代码后，是否仍能确保对 #1046 的修复效果？是否需要补充特定的回归测试用例来验证兼容性？感谢您的分析。

[CaroLe-prw]

@CaroLe-prw Hi, this code was originally introduced in PR #1057 to resolve issues #1046. After its removal in this PR, would the fix for #1046 still hold effectively? Would you consider adding targeted regression tests to ensure backward compatibility? Your insights would be appreciated.嗨，这段代码最初是在 PR #1057 中引入的，用于解决问题 #1046 。在这次 PR 中移除后，问题 #1046 的修复是否仍然有效？您是否考虑添加有针对性的回归测试以确保向后兼容性？您的见解将不胜感激。

请问，这部分代码最初是 PR #1057 为解决 issues #1046 引入的。当前 PR 移除该代码后，是否仍能确保对 #1046 的修复效果？是否需要补充特定的回归测试用例来验证兼容性？感谢您的分析。

@linwumingshi ​​ Hello, I've recompiled the build and fixed the issue. Below are the test results for the fixed version.​：

openapi:

swagger: