[ISSUE #13869] fix Error creating bean with name 'consoleHealthContro…

[herodotus-ecosystem]

…ller'

Please do not create a Pull Request without creating an issue first.

What is the purpose of the change

fix: #13869

Brief changelog

[ISSUE #13869] fix Error creating bean with name 'consoleHealthController' problem

Verifying this change

1. ConsoleHealthController 需要以构造函数的方式注入 HealthProxy Bean
2. HealthProxy 需要以构造函数的方式注入 HealthHandler Bean
3. HealthHandler 的实现类有两个 HealthInnerHandler 和 HealthRemoteHandler 两个，nacos.deployment.type 默认值为 merge，即如果配置文件中没有 nacos.deployment.type 属性应该默认注入 HealthInnerHandler

Follow this checklist to help us incorporate your contribution quickly and easily:

• [√] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• [√] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
• [√] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• [√] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
• [√] Run mvn -B clean package apache-rat:check findbugs:findbugs -Dmaven.test.skip=true to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test to make sure integration-test pass.

[github-actions]

Thanks for your this PR. 🙏
Please check again for your PR changes whether contains any usage/api/configuration change such as Add new API , Add new configuration, Change default value of configuration.
If so, please add or update documents(markdown type) in docs/next/ for repository nacos-group/nacos-group.github.io

---

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

[wuyfee]

$\color{red}{FAILURE}$
DETAILS
✅ - docker: success
❌ - deploy (standalone & cluster & standalone_auth): failure
❌ - e2e-java-test (standalone & cluster & standalone_auth): skipped
❌ - e2e-go-test (standalone & cluster): skipped
❌ - e2e-cpp-test (standalone & cluster): skipped
❌ - e2e-csharp-test (standalone & cluster): skipped
❌ - e2e-nodejs-test (standalone & cluster): skipped
❌ - e2e-python-test (standalone & cluster): skipped
✅ - clean (standalone & cluster & standalone_auth): success