support load .env config from nacos

[shiyiyue1102]

Summary

support load .env config from nacos

Similar to #11210

Resolved #11064

Tip

Close issue syntax: Fixes #<issue number> or Resolves #<issue number>, see documentation for more details.

Screenshots

Before	After
...	...

Checklist

Important

Please review the checklist below before submitting your pull request.

• This change requires a documentation update, included: Dify Document
• I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
• I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
• I've updated the documentation accordingly.
• I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods

[crazywoola]

Please fix the tests in CI

[Copilot]

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

[Copilot]

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (2)

api/configs/remote_settings_sources/nacos/utils.py:2

• [nitpick] The use of 'self' as the first parameter in this standalone function is potentially confusing. Consider renaming it to something more appropriate (e.g. 'content_parser' if needed) or refactoring this logic as a static method.

def _parse_config(self, content: str) -> dict[str, str]:

api/configs/remote_settings_sources/nacos/init.py:37

• [nitpick] The log message tag '[get-access-token]' is misleading in the context of the async initialization of the settings source. Consider updating it to reflect that the error occurred during Nacos config fetching.

logger.exception("[get-access-token] exception occurred")

[shiyiyue1102]

Why hasn't CI been running even after a day has passed? @crazywoola

[crazywoola]

Not sure about the CI pipeline, I have closed it and reopen the PR again.